summaryrefslogtreecommitdiff
path: root/arch/s390
diff options
context:
space:
mode:
authorChristian Borntraeger <borntraeger@de.ibm.com>2013-05-08 15:25:38 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2013-05-15 13:09:07 +0200
commitbb4b42ce0ca36af8c113587ab64b138b3cf5459c (patch)
treecc9d66a088378d1d409220e632c54466912cf40e /arch/s390
parent617e164c35c94c936e3632b387d6dbb3d80c2c02 (diff)
downloadlinux-3.10-bb4b42ce0ca36af8c113587ab64b138b3cf5459c.tar.gz
linux-3.10-bb4b42ce0ca36af8c113587ab64b138b3cf5459c.tar.bz2
linux-3.10-bb4b42ce0ca36af8c113587ab64b138b3cf5459c.zip
s390: fix gmap_ipte_notifier vs. software dirty pages
On heavy paging load some guest cpus started to loop in gmap_ipte_notify. This was visible as stalled cpus inside the guest. The gmap_ipte_notifier tries to map a user page and then made sure that the pte is valid and writable. Turns out that with the software change bit tracking the pte can become read-only (and only software writable) if the page is clean. Since we loop in this code, the page would stay clean and, therefore, be never writable again. Let us just use fixup_user_fault, that guarantees to call handle_mm_fault. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390')
-rw-r--r--arch/s390/mm/pgtable.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/s390/mm/pgtable.c b/arch/s390/mm/pgtable.c
index 7805ddca833..18dc417aaf7 100644
--- a/arch/s390/mm/pgtable.c
+++ b/arch/s390/mm/pgtable.c
@@ -677,8 +677,7 @@ int gmap_ipte_notify(struct gmap *gmap, unsigned long start, unsigned long len)
break;
}
/* Get the page mapped */
- if (get_user_pages(current, gmap->mm, addr, 1, 1, 0,
- NULL, NULL) != 1) {
+ if (fixup_user_fault(current, gmap->mm, addr, FAULT_FLAG_WRITE)) {
rc = -EFAULT;
break;
}