mm/hugetlb: Fix selftest failures with write check
Subsystems (3)
v2 cover mm/hugetlb: Fix selftest failures with write check
v2:
- Fix the commit message of patch 1, replacing CoW with wr-unprotect example
Currently akpm mm-unstable fails with uffd hugetlb private mapping test randomly on a write check.
The initial bisection of that points to the recent pmd unshare series, but it turns out there's no direction relationship with the series but only some timing change caused the race to start trigger.
The race should be fixed in patch 1. Patch 2 is a trivial cleanup on the similar race with hugetlb migrations, patch 3 comment on the write check so when anyone read it again it'll be clear why it's there.
Thanks,
Peter Xu (3):
mm/hugetlb: Fix race condition of uffd missing/minor handling mm/hugetlb: Use hugetlb_pte_stable in migration race check mm/selftest: uffd: Explain the write missing fault check
mm/hugetlb.c | 62 ++++++++++++++++++++---- tools/testing/selftests/vm/userfaultfd.c | 22 ++++++++- 2 files changed, 73 insertions(+), 11 deletions(-)
Signature · 1 line
2.37.3
PATCH v2 1/3 mm/hugetlb: Fix race condition of uffd missing/minor handling
After the recent rework patchset of hugetlb locking on pmd sharing, kselftest for userfaultfd sometimes fails on hugetlb private tests with unexpected write fault checks.
It turns out there's nothing wrong within the locking series regarding this matter, but it could have changed the timing of threads so it can trigger an old bug.
The real bug is when we call hugetlb_no_page() we're not with the pgtable lock. It means we're reading the pte values lockless. It's perfectly fine in most cases because before we do normal page allocations we'll take the lock and check pte_same() again. However before that, there are actually two paths on userfaultfd missing/minor handling that may directly move on with the fault process without checking the pte values.
It means for these two paths we may be generating an uffd message based on an unstable pte, while an unstable pte can legally be anything as long as the modifier holds the pgtable lock.
One example, which is also what happened in the failing kselftest and caused the test failure, is that for private mappings wr-protection changes can happen on one page. While hugetlb_change_protection() generally requires pte being cleared before being changed, then there can be a race condition like:
thread 1 thread 2
-------- --------
UFFDIO_WRITEPROTECT hugetlb_fault
hugetlb_change_protection
pgtable_lock()
huge_ptep_modify_prot_start
pte==NULL hugetlb_no_page
generate uffd missing event even if page existed!!
huge_ptep_modify_prot_commit
pgtable_unlock()
Fix this by recheck the pte after pgtable lock for both userfaultfd missing & minor fault paths.
This bug should have been around starting from uffd hugetlb introduced, so attaching a Fixes to the commit. Also attach another Fixes to the minor support commit for easier tracking.
Note that userfaultfd is actually fine with false positives (e.g. caused by pte changed), but not wrong logical events (e.g. caused by reading a pte during changing). The latter can confuse the userspace, so the strictness is very much preferred. E.g., MISSING event should never happen on the page after UFFDIO_COPY has correctly installed the page and returned.
--- mm/hugetlb.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 49 insertions(+), 6 deletions(-)
mm/hugetlb.c +49 -6
@@ -5521,6 +5521,23 @@ static inline vm_fault_t hugetlb_handle_userfault(struct vm_area_struct *vma,return ret; } +/* +* Recheck pte with pgtable lock. Returns true if pte didn't change, or +* false if pte changed or is changing. +*/ +static bool hugetlb_pte_stable (struct hstate *h,struct mm_struct *mm, +pte_t *ptep,pte_t old_pte) +{ +spinlock_t *ptl; +bool same; + + ptl =huge_pte_lock (h, mm, ptep); + same =pte_same (huge_ptep_get (ptep), old_pte); +spin_unlock (ptl); + +return same; +} + static vm_fault_t hugetlb_no_page(struct mm_struct *mm, struct vm_area_struct *vma, struct address_space *mapping, pgoff_t idx,
@@ -5562,9 +5579,30 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm, goto out;/* Check for page in userfault range */ if (userfaultfd_missing (vma)) { - ret =hugetlb_handle_userfault (vma, mapping, idx, - flags, haddr, address, -VM_UFFD_MISSING ); +/* +* Since hugetlb_no_page() was examining pte +* without pgtable lock, we need to re-test under +* lock because the pte may not be stable and could +* have changed from under us. Try to detect +* either changed or during-changing ptes and retry +* properly when needed. +* +* Note that userfaultfd is actually fine with +* false positives (e.g. caused by pte changed), +* but not wrong logical events (e.g. caused by +* reading a pte during changing). The latter can +* confuse the userspace, so the strictness is very +* much preferred. E.g., MISSING event should +* never happen on the page after UFFDIO_COPY has +* correctly installed the page and returned. +*/ +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) + ret =hugetlb_handle_userfault ( + vma, mapping, idx, flags, haddr, + address,VM_UFFD_MISSING ); +else +/* Retry the fault */ + ret =0 ; goto out; }
@@ -5634,9 +5672,14 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,if (userfaultfd_minor (vma)) {unlock_page (page);put_page (page); - ret =hugetlb_handle_userfault (vma, mapping, idx, - flags, haddr, address, -VM_UFFD_MINOR ); +/* See comment in userfaultfd_missing() block above */ +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) + ret =hugetlb_handle_userfault ( + vma, mapping, idx, flags, haddr, + address,VM_UFFD_MINOR ); +else +/* Retry the fault */ + ret =0 ; goto out; } }
Signature · 1 line
2.37.3
Re: [PATCH v2 1/3] mm/hugetlb: Fix race condition of uffd missing/minor handling
Quoted 60 lines · Peter Xu
After the recent rework patchset of hugetlb locking on pmd sharing, kselftest for userfaultfd sometimes fails on hugetlb private tests with unexpected write fault checks.
It turns out there's nothing wrong within the locking series regarding this matter, but it could have changed the timing of threads so it can trigger an old bug.
The real bug is when we call
hugetlb_no_page()we're not with the pgtable lock. It means we're reading the pte values lockless. It's perfectly fine in most cases because before we do normal page allocations we'll take the lock and checkpte_same()again. However before that, there are actually two paths on userfaultfd missing/minor handling that may directly move on with the fault process without checking the pte values.It means for these two paths we may be generating an uffd message based on an unstable pte, while an unstable pte can legally be anything as long as the modifier holds the pgtable lock.
One example, which is also what happened in the failing kselftest and caused the test failure, is that for private mappings wr-protection changes can happen on one page. While
hugetlb_change_protection()generally requires pte being cleared before being changed, then there can be a race condition like:thread 1 thread 2
-------- --------
UFFDIO_WRITEPROTECThugetlb_fault
hugetlb_change_protection
pgtable_lock()
huge_ptep_modify_prot_start
pte==NULLhugetlb_no_page
generate uffd missing event even if page existed!!
huge_ptep_modify_prot_commit
pgtable_unlock()Fix this by recheck the pte after pgtable lock for both userfaultfd missing & minor fault paths.
This bug should have been around starting from uffd hugetlb introduced, so attaching a Fixes to the commit. Also attach another Fixes to the minor support commit for easier tracking.
Note that userfaultfd is actually fine with false positives (e.g. caused by pte changed), but not wrong logical events (e.g. caused by reading a pte during changing). The latter can confuse the userspace, so the strictness is very much preferred. E.g., MISSING event should never happen on the page after
UFFDIO_COPYhas correctly installed the page and returned.Cc Andrea Arcangeli <[email protected]>Cc Mike Kravetz <[email protected]>Cc Axel Rasmussen <[email protected]>Cc Nadav Amit <[email protected]>Fixes 1a1aad8a9b7b ("userfaultfd: hugetlbfs: add userfaultfd hugetlb hook")Fixes 7677f7fd8be7 ("userfaultfd: add minor fault registration mode")Co-developed-by Mike Kravetz <[email protected]>Signed-off-by Peter Xu <[email protected]>
Quoted 3 lines
--- mm/hugetlb.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 49 insertions(+), 6 deletions(-)
Thanks.
Do note that this will not apply on top of "mm: hugetlb: fix UAF in hugetlb_handle_userfault" which is already in Andrew's tree. However, required changes should be simple.
Signature · 1 line
Mike Kravetz
Quoted 84 lines
mm/hugetlb.c +49
-6@@ -5521,6 +5521,23 @@ static inline vm_fault_t hugetlb_handle_userfault(struct vm_area_struct *vma,return ret; } +/* +* Recheck pte with pgtable lock. Returns true if pte didn't change, or +* false if pte changed or is changing. +*/ +static bool hugetlb_pte_stable (struct hstate *h,struct mm_struct *mm, +pte_t *ptep,pte_t old_pte) +{ +spinlock_t *ptl; +bool same; + + ptl =huge_pte_lock (h, mm, ptep); + same =pte_same (huge_ptep_get (ptep), old_pte); +spin_unlock (ptl); + +return same; +} + static vm_fault_t hugetlb_no_page(struct mm_struct *mm, struct vm_area_struct *vma, struct address_space *mapping, pgoff_t idx,@@ -5562,9 +5579,30 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm, goto out;/* Check for page in userfault range */ if (userfaultfd_missing (vma)) { - ret =hugetlb_handle_userfault (vma, mapping, idx, - flags, haddr, address, -VM_UFFD_MISSING ); +/* +* Since hugetlb_no_page() was examining pte +* without pgtable lock, we need to re-test under +* lock because the pte may not be stable and could +* have changed from under us. Try to detect +* either changed or during-changing ptes and retry +* properly when needed. +* +* Note that userfaultfd is actually fine with +* false positives (e.g. caused by pte changed), +* but not wrong logical events (e.g. caused by +* reading a pte during changing). The latter can +* confuse the userspace, so the strictness is very +* much preferred. E.g., MISSING event should +* never happen on the page after UFFDIO_COPY has +* correctly installed the page and returned. +*/ +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) + ret =hugetlb_handle_userfault ( + vma, mapping, idx, flags, haddr, + address,VM_UFFD_MISSING ); +else +/* Retry the fault */ + ret =0 ; goto out; }@@ -5634,9 +5672,14 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,if (userfaultfd_minor (vma)) {unlock_page (page);put_page (page); - ret =hugetlb_handle_userfault (vma, mapping, idx, - flags, haddr, address, -VM_UFFD_MINOR ); +/* See comment in userfaultfd_missing() block above */ +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) + ret =hugetlb_handle_userfault ( + vma, mapping, idx, flags, haddr, + address,VM_UFFD_MINOR ); +else +/* Retry the fault */ + ret =0 ; goto out; } }Signature · 1 line
2.37.3
Re: [PATCH v2 1/3] mm/hugetlb: Fix race condition of uffd missing/minor handling
Quoted 3 lines · Mike Kravetz
Do note that this will not apply on top of "mm: hugetlb: fix UAF in
hugetlb_handle_userfault" which is already in Andrew's tree. However, required changes should be simple.
Thanks for the heads up, I'll rebase.
Quoted 2 lines
Reviewed-by Mike Kravetz <[email protected]>
Thanks,
Signature · 1 line
Peter Xu
Re: [PATCH v2 1/3] mm/hugetlb: Fix race condition of uffd missing/minor handling
In reply to Peter XuQuoted 110 lines · Peter Xu
After the recent rework patchset of hugetlb locking on pmd sharing, kselftest for userfaultfd sometimes fails on hugetlb private tests with unexpected write fault checks.
It turns out there's nothing wrong within the locking series regarding this matter, but it could have changed the timing of threads so it can trigger an old bug.
The real bug is when we call
hugetlb_no_page()we're not with the pgtable lock. It means we're reading the pte values lockless. It's perfectly fine in most cases because before we do normal page allocations we'll take the lock and checkpte_same()again. However before that, there are actually two paths on userfaultfd missing/minor handling that may directly move on with the fault process without checking the pte values.It means for these two paths we may be generating an uffd message based on an unstable pte, while an unstable pte can legally be anything as long as the modifier holds the pgtable lock.
One example, which is also what happened in the failing kselftest and caused the test failure, is that for private mappings wr-protection changes can happen on one page. While
hugetlb_change_protection()generally requires pte being cleared before being changed, then there can be a race condition like:thread 1 thread 2
-------- --------
UFFDIO_WRITEPROTECThugetlb_fault
hugetlb_change_protection
pgtable_lock()
huge_ptep_modify_prot_start
pte==NULLhugetlb_no_page
generate uffd missing event even if page existed!!
huge_ptep_modify_prot_commit
pgtable_unlock()Fix this by recheck the pte after pgtable lock for both userfaultfd missing & minor fault paths.
This bug should have been around starting from uffd hugetlb introduced, so attaching a Fixes to the commit. Also attach another Fixes to the minor support commit for easier tracking.
Note that userfaultfd is actually fine with false positives (e.g. caused by pte changed), but not wrong logical events (e.g. caused by reading a pte during changing). The latter can confuse the userspace, so the strictness is very much preferred. E.g., MISSING event should never happen on the page after
UFFDIO_COPYhas correctly installed the page and returned.Cc Andrea Arcangeli <[email protected]>Cc Mike Kravetz <[email protected]>Cc Axel Rasmussen <[email protected]>Cc Nadav Amit <[email protected]>Fixes 1a1aad8a9b7b ("userfaultfd: hugetlbfs: add userfaultfd hugetlb hook")Fixes 7677f7fd8be7 ("userfaultfd: add minor fault registration mode")Co-developed-by Mike Kravetz <[email protected]>Signed-off-by Peter Xu <[email protected]>--- mm/hugetlb.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 49 insertions(+), 6 deletions(-)mm/hugetlb.c +28
-3@@ -5521,6 +5521,23 @@ static inline vm_fault_t hugetlb_handle_userfault(struct vm_area_struct *vma,return ret; } +/* +* Recheck pte with pgtable lock. Returns true if pte didn't change, or +* false if pte changed or is changing. +*/ +static bool hugetlb_pte_stable (struct hstate *h,struct mm_struct *mm, +pte_t *ptep,pte_t old_pte) +{ +spinlock_t *ptl; +bool same; + + ptl =huge_pte_lock (h, mm, ptep); + same =pte_same (huge_ptep_get (ptep), old_pte); +spin_unlock (ptl); + +return same; +} + static vm_fault_t hugetlb_no_page(struct mm_struct *mm, struct vm_area_struct *vma, struct address_space *mapping, pgoff_t idx,@@ -5562,9 +5579,30 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm, goto out;/* Check for page in userfault range */ if (userfaultfd_missing (vma)) { - ret =hugetlb_handle_userfault (vma, mapping, idx, - flags, haddr, address, -VM_UFFD_MISSING ); +/* +* Since hugetlb_no_page() was examining pte +* without pgtable lock, we need to re-test under +* lock because the pte may not be stable and could +* have changed from under us. Try to detect +* either changed or during-changing ptes and retry +* properly when needed. +* +* Note that userfaultfd is actually fine with +* false positives (e.g. caused by pte changed), +* but not wrong logical events (e.g. caused by
mm/hugetlb.c static vm_fault_t hugetlb_no_page(struct mm_struct *mm, · line 5602
Quoted 10 lines
mm/hugetlb.c +10
-0+* reading a pte during changing). The latter can +* confuse the userspace, so the strictness is very +* much preferred. E.g., MISSING event should +* never happen on the page after UFFDIO_COPY has +* correctly installed the page and returned. +*/ +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) + ret =hugetlb_handle_userfault ( + vma, mapping, idx, flags, haddr, + address,VM_UFFD_MISSING );
That looks kind-of ugly now. I wonder if it would be worth factoring that handling out into a separate function and reusing it at two places. Would get rid of one level of code indent at least.
Apart from that, LGTM. Although the lockless reading of the PTE screams for more trouble in the future :)
Signature · 3 lines
Thanks, David / dhildenb
Re: [PATCH v2 1/3] mm/hugetlb: Fix race condition of uffd missing/minor handling
Quoted 6 lines · David Hildenbrand
That looks kind-of ugly now. I wonder if it would be worth factoring that handling out into a separate function and reusing it at two places. Would get rid of one level of code indent at least.
Apart from that, LGTM. Although the lockless reading of the PTE screams for more trouble in the future :)
Right there's potential to further rework it, I am just not sure whether that could be common enough so that we can start to take pg lock for the whole region (then we'll need to release for either page lock or alloc). Not really sure whether that'll be worth the effort.
However, at least uffd minor doesn't really need the page lock so we can optimize it with a find_get_page() earlier then the missing mode can be moved over too (following a lock_page?). Maybe I should give it a shot.
For this one I'll keep it simple since I think we should have it for stable too. Thanks for the review!
Signature · 1 line
Peter Xu
PATCH v2 2/3 mm/hugetlb: Use hugetlb_pte_stable in migration race check
In reply to Peter XuAfter hugetlb_pte_stable() introduced, we can also rewrite the migration race condition against page allocation to use the new helper too.
--- mm/hugetlb.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
mm/hugetlb.c +3 -4
@@ -5620,11 +5620,10 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,* here. Before returning error, get ptl and make * sure there really is no pte entry. */ - ptl =huge_pte_lock (h, mm, ptep); - ret =0 ; -if (huge_pte_none (huge_ptep_get (ptep))) +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) ret =vmf_error (PTR_ERR (page)); -spin_unlock (ptl); +else + ret =0 ; goto out; }clear_huge_page (page, address,pages_per_huge_page (h));
Signature · 1 line
2.37.3
Re: [PATCH v2 2/3] mm/hugetlb: Use hugetlb_pte_stable in migration race check
Quoted 7 lines · Peter Xu
After
hugetlb_pte_stable()introduced, we can also rewrite the migration race condition against page allocation to use the new helper too.Signed-off-by Peter Xu <[email protected]>--- mm/hugetlb.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
Signature · 1 line
Mike Kravetz
Quoted 23 lines
mm/hugetlb.c +3
-4@@ -5620,11 +5620,10 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,* here. Before returning error, get ptl and make * sure there really is no pte entry. */ - ptl =huge_pte_lock (h, mm, ptep); - ret =0 ; -if (huge_pte_none (huge_ptep_get (ptep))) +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) ret =vmf_error (PTR_ERR (page)); -spin_unlock (ptl); +else + ret =0 ; goto out; }clear_huge_page (page, address,pages_per_huge_page (h));Signature · 1 line
2.37.3
Re: [PATCH v2 2/3] mm/hugetlb: Use hugetlb_pte_stable in migration race check
In reply to Peter XuQuoted 17 lines · Peter Xu
After
hugetlb_pte_stable()introduced, we can also rewrite the migration race condition against page allocation to use the new helper too.Signed-off-by Peter Xu <[email protected]>--- mm/hugetlb.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)mm/hugetlb.c +0
-1@@ -5620,11 +5620,10 @@ static vm_fault_t hugetlb_no_page(struct mm_struct *mm,* here. Before returning error, get ptl and make * sure there really is no pte entry. */ - ptl =huge_pte_lock (h, mm, ptep);
mm/hugetlb.c static vm_fault_t hugetlb_no_page(struct mm_struct *mm, · line 5629
Quoted 10 lines
mm/hugetlb.c +3
-3- ret =0 ; -if (huge_pte_none (huge_ptep_get (ptep))) +if (hugetlb_pte_stable (h, mm, ptep, old_pte)) ret =vmf_error (PTR_ERR (page)); -spin_unlock (ptl); +else + ret =0 ; goto out; }clear_huge_page (page, address,pages_per_huge_page (h));
Signature · 3 lines
Thanks, David / dhildenb
PATCH v2 3/3 mm/selftest: uffd: Explain the write missing fault check
In reply to Peter XuIt's not obvious why we had a write check for each of the missing messages, especially when it should be a locking op. Add a rich comment for that, and also try to explain its good side and limitations, so that if someone hit it again for either a bug or a different glibc impl there'll be some clue to start with.
--- tools/testing/selftests/vm/userfaultfd.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
tools/testing/selftests/vm/userfaultfd.c +21 -1
@@ -774,7 +774,27 @@ static void uffd_handle_page_fault(struct uffd_msg *msg,continue_range (uffd, msg->arg.pagefault.address, page_size); stats->minor_faults++; }else { -/* Missing page faults */ +/* +* Missing page faults. +* +* Here we force a write check for each of the missing mode +* faults. It's guaranteed because the only threads that +* will trigger uffd faults are the locking threads, and +* their first instruction to touch the missing page will +* always be pthread_mutex_lock(). +* +* Note that here we relied on an NPTL glibc impl detail to +* always read the lock type at the entry of the lock op +* (pthread_mutex_t.__data.__type, offset 0x10) before +* doing any locking operations to guarantee that. It's +* actually not good to rely on this impl detail because +* logically a pthread-compatible lib can implement the +* locks without types and we can fail when linking with +* them. However since we used to find bugs with this +* strict check we still keep it around. Hopefully this +* could be a good hint when it fails again. If one day +* it'll break on some other impl of glibc we'll revisit. +*/ if (msg->arg.pagefault.flags &UFFD_PAGEFAULT_FLAG_WRITE )err ("unexpected write fault" );
Signature · 1 line
2.37.3
Re: [PATCH v2 3/3] mm/selftest: uffd: Explain the write missing fault check
Quoted 5 lines · Peter Xu
It's not obvious why we had a write check for each of the missing messages, especially when it should be a locking op. Add a rich comment for that, and also try to explain its good side and limitations, so that if someone hit it again for either a bug or a different glibc impl there'll be some clue to start with.
Thanks! It did take a while to understand all this, so the comment is appropriate.
Quoted 5 lines
Signed-off-by Peter Xu <[email protected]>--- tools/testing/selftests/vm/userfaultfd.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
Signature · 1 line
Mike Kravetz
Quoted 37 lines
tools/testing/selftests/vm/userfaultfd.c +21
-1@@ -774,7 +774,27 @@ static void uffd_handle_page_fault(struct uffd_msg *msg,continue_range (uffd, msg->arg.pagefault.address, page_size); stats->minor_faults++; }else { -/* Missing page faults */ +/* +* Missing page faults. +* +* Here we force a write check for each of the missing mode +* faults. It's guaranteed because the only threads that +* will trigger uffd faults are the locking threads, and +* their first instruction to touch the missing page will +* always be pthread_mutex_lock(). +* +* Note that here we relied on an NPTL glibc impl detail to +* always read the lock type at the entry of the lock op +* (pthread_mutex_t.__data.__type, offset 0x10) before +* doing any locking operations to guarantee that. It's +* actually not good to rely on this impl detail because +* logically a pthread-compatible lib can implement the +* locks without types and we can fail when linking with +* them. However since we used to find bugs with this +* strict check we still keep it around. Hopefully this +* could be a good hint when it fails again. If one day +* it'll break on some other impl of glibc we'll revisit. +*/ if (msg->arg.pagefault.flags &UFFD_PAGEFAULT_FLAG_WRITE )err ("unexpected write fault" );Signature · 1 line
2.37.3
Re: [PATCH v2 3/3] mm/selftest: uffd: Explain the write missing fault check
In reply to Peter XuQuoted 34 lines · Peter Xu
It's not obvious why we had a write check for each of the missing messages, especially when it should be a locking op. Add a rich comment for that, and also try to explain its good side and limitations, so that if someone hit it again for either a bug or a different glibc impl there'll be some clue to start with.
Signed-off-by Peter Xu <[email protected]>--- tools/testing/selftests/vm/userfaultfd.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)tools/testing/selftests/vm/userfaultfd.c +14
-1@@ -774,7 +774,27 @@ static void uffd_handle_page_fault(struct uffd_msg *msg,continue_range (uffd, msg->arg.pagefault.address, page_size); stats->minor_faults++; }else { -/* Missing page faults */ +/* +* Missing page faults. +* +* Here we force a write check for each of the missing mode +* faults. It's guaranteed because the only threads that +* will trigger uffd faults are the locking threads, and +* their first instruction to touch the missing page will +* always be pthread_mutex_lock(). +* +* Note that here we relied on an NPTL glibc impl detail to +* always read the lock type at the entry of the lock op +* (pthread_mutex_t.__data.__type, offset 0x10) before +* doing any locking operations to guarantee that. It's +* actually not good to rely on this impl detail because
tools/testing/selftests/vm/userfaultfd.c static void uffd_handle_page_fault(struct uffd_msg *msg, · line 800
Quoted 10 lines
tools/testing/selftests/vm/userfaultfd.c +7
-0+* logically a pthread-compatible lib can implement the +* locks without types and we can fail when linking with +* them. However since we used to find bugs with this +* strict check we still keep it around. Hopefully this +* could be a good hint when it fails again. If one day +* it'll break on some other impl of glibc we'll revisit. +*/ if (msg->arg.pagefault.flags &UFFD_PAGEFAULT_FLAG_WRITE )err ("unexpected write fault" );
Signature · 3 lines
Thanks, David / dhildenb