mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY properly
Subsystems (4)
cover mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY properly
Derrick reports that in some cases where pread() would fail with -EIO and mmap()+access would generate a SIGBUS signal, MADV_POPULATE_READ / MADV_POPULATE_WRITE will keep retrying forever and not fail with -EFAULT.
It all boils down to missing VM_FAULT_RETRY handling. Let's try to handle that in a better way, similar to how ordinary GUP handles it.
Details in patch #1. In short, move special MADV_POPULATE_(READ|WRITE) VMA handling into __get_user_pages(), and make faultin_page_range() call __get_user_pages_locked(), which handles VM_FAULT_RETRY. Further, avoid the now-useless madvise VMA walk, because __get_user_pages() will perform the VMA lookup either way.
I briefly played with handling the FOLL_MADV_POPULATE checks in __get_user_pages() a bit differently, integrating them with existing handling, but it ended up looking worse. So I decided to keep it simple.
Likely, we need better selftests, but the reproducer from Darrick might be a bit hard to convert into a simple selftest.
Note that using mlock() in Darricks reproducer results in a similar endless retry. Likely, that is not what we want, and we should handle VM_FAULT_RETRY in populate_vma_page_range() / __mm_populate() as well. However, similarly using __get_user_pages_locked() might be more complicated, because of the advanced VMA handling in populate_vma_page_range().
Further, most populate_vma_page_range() callers simply ignore the return values, so it's unclear in which cases we expect to just silently fail, or where we'd want to retry+fail or endlessly retry instead.
David Hildenbrand (2):
mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY
properly
mm/madvise: don't perform madvise VMA walk for
MADV_POPULATE_(READ|WRITE)
mm/gup.c | 54 ++++++++++++++++++++++++++++++--------------------- mm/internal.h | 10 ++++++---- mm/madvise.c | 43 +++++++++++++--------------------------- 3 files changed, 52 insertions(+), 55 deletions(-)
base-commit: f48159f866f422371bb1aad10eb4d05b29ca4d8c
Signature · 1 line
2.43.2
PATCH 1/2 mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY properly
Darrick reports that in some cases where pread() would fail with -EIO and mmap()+access would generate a SIGBUS signal, MADV_POPULATE_READ / MADV_POPULATE_WRITE will keep retrying forever and not fail with -EFAULT.
While the madvise() call can be interrupted by a signal, this is not the desired behavior. MADV_POPULATE_READ / MADV_POPULATE_WRITE should behave like page faults in that case: fail and not retry forever.
A reproducer can be found at [1].
The reason is that __get_user_pages(), as called by faultin_vma_page_range(), will not handle VM_FAULT_RETRY in a proper
way: it will simply return 0 when VM_FAULT_RETRY happened, making madvise_populate()->faultin_vma_page_range() retry again and again, never setting FOLL_TRIED->FAULT_FLAG_TRIED for __get_user_pages().
__get_user_pages_locked() does what we want, but duplicating that logic in faultin_vma_page_range() feels wrong.
So let's use __get_user_pages_locked() instead, that will detect VM_FAULT_RETRY and set FOLL_TRIED when retrying, making the fault handler return VM_FAULT_SIGBUS (VM_FAULT_ERROR) at some point, propagating -EFAULT from faultin_page() to __get_user_pages(), all the way to madvise_populate().
But, there is an issue: __get_user_pages_locked() will end up re-taking the MM lock and then __get_user_pages() will do another VMA lookup. In the meantime, the VMA layout could have changed and we'd fail with different error codes than we'd want to.
As __get_user_pages() will currently do a new VMA lookup either way, let it do the VMA handling in a different way, controlled by a new FOLL_MADV_POPULATE flag, effectively moving these checks from madvise_populate() + faultin_page_range() in there.
With this change, Darricks reproducer properly fails with -EFAULT, as documented for MADV_POPULATE_READ / MADV_POPULATE_WRITE.
[1] https://lore.kernel.org/all/20240313171936.GN1927156@frogsfrogsfrogs/
--- mm/gup.c | 54 ++++++++++++++++++++++++++++++--------------------- mm/internal.h | 10 ++++++---- mm/madvise.c | 17 ++-------------- 3 files changed, 40 insertions(+), 41 deletions(-)
mm/gup.c +32 -22
@@ -1206,6 +1206,22 @@ static long __get_user_pages(struct mm_struct *mm,/* first iteration or cross vma bound */ if (!vma || start >= vma->vm_end) { +/* +* MADV_POPULATE_(READ|WRITE) wants to handle VMA +* lookups+error reporting differently. +*/ +if (gup_flags &FOLL_MADV_POPULATE ) { + vma =vma_lookup (mm, start); +if (!vma) { + ret = -ENOMEM ; + goto out; + } +if (check_vma_flags (vma, gup_flags)) { + ret = -EINVAL ; + goto out; + } + goto retry; + } vma =gup_vma_lookup (mm, start);if (!vma &&in_gate_area (mm, start)) { ret = get_gate_page(mm, start & PAGE_MASK,
@@ -1683,35 +1699,35 @@ long populate_vma_page_range(struct vm_area_struct *vma, }/* -* faultin_vma_page_range() - populate (prefault) page tables inside the -* given VMA range readable/writable +* faultin_page_range() - populate (prefault) page tables inside the +* given range readable/writable * * This takes care of mlocking the pages, too, if VM_LOCKED is set. * -* @vma: target vma +* @mm: the mm to populate page tables in * @start: start address * @end: end address * @write: whether to prefault readable or writable * @locked: whether the mmap_lock is still held * -* Returns either number of processed pages in the vma, or a negative error -* code on error (see __get_user_pages()). +* Returns either number of processed pages in the MM, or a negative error +* code on error (see __get_user_pages()). Note that this function reports +* errors related to VMAs, such as incompatible mappings, as expected by +* MADV_POPULATE_(READ|WRITE). * -* vma->vm_mm->mmap_lock must be held. The range must be page-aligned and -* covered by the VMA. If it's released, *@locked will be set to 0. +* The range must be page-aligned. +* +* mm->mmap_lock must be held. If it's released, *@locked will be set to 0. */ -long faultin_vma_page_range (struct vm_area_struct *vma,unsigned long start, -unsigned long end,bool write,int *locked) +long faultin_page_range (struct mm_struct *mm,unsigned long start, +unsigned long end,bool write,int *locked) { -struct mm_struct *mm = vma->vm_mm;unsigned long nr_pages = (end - start) /PAGE_SIZE ;int gup_flags;long ret;VM_BUG_ON (!PAGE_ALIGNED (start));VM_BUG_ON (!PAGE_ALIGNED (end)); -VM_BUG_ON_VMA (start < vma->vm_start, vma); -VM_BUG_ON_VMA (end > vma->vm_end, vma);mmap_assert_locked (mm);/*
@@ -1723,19 +1739,13 @@ long faultin_vma_page_range(struct vm_area_struct *vma, unsigned long start,* a poisoned page. * !FOLL_FORCE: Require proper access permissions. */ - gup_flags =FOLL_TOUCH |FOLL_HWPOISON |FOLL_UNLOCKABLE ; + gup_flags =FOLL_TOUCH |FOLL_HWPOISON |FOLL_UNLOCKABLE | +FOLL_MADV_POPULATE ;if (write) gup_flags |=FOLL_WRITE ; -/* -* We want to report -EINVAL instead of -EFAULT for any permission -* problems or incompatible mappings. -*/ -if (check_vma_flags (vma, gup_flags)) -return -EINVAL ; - - ret =__get_user_pages (mm, start, nr_pages, gup_flags, -NULL , locked); + ret =__get_user_pages_locked (mm, start, nr_pages,NULL , locked, + gup_flags);lru_add_drain ();return ret; }
mm/internal.h +6 -4
@@ -686,9 +686,8 @@ struct anon_vma *folio_anon_vma(struct folio *folio);void unmap_mapping_folio (struct folio *folio);extern long populate_vma_page_range (struct vm_area_struct *vma,unsigned long start,unsigned long end,int *locked); -extern long faultin_vma_page_range (struct vm_area_struct *vma, -unsigned long start,unsigned long end, -bool write,int *locked); +extern long faultin_page_range (struct mm_struct *mm,unsigned long start, +unsigned long end,bool write,int *locked);extern bool mlock_future_ok (struct mm_struct *mm,unsigned long flags,unsigned long bytes);
@@ -1127,10 +1126,13 @@ enum {FOLL_FAST_ONLY =1 <<20 ,/* allow unlocking the mmap lock */ FOLL_UNLOCKABLE =1 <<21 , +/* VMA lookup+checks compatible with MADV_POPULATE_(READ|WRITE) */ + FOLL_MADV_POPULATE = 1 << 22, };#define INTERNAL_GUP_FLAGS (FOLL_TOUCH | FOLL_TRIED | FOLL_REMOTE | FOLL_PIN | \ - FOLL_FAST_ONLY | FOLL_UNLOCKABLE) + FOLL_FAST_ONLY | FOLL_UNLOCKABLE | \ + FOLL_MADV_POPULATE)/* * Indicates for which pages that are write-protected in the page table,
mm/madvise.c +2 -15
@@ -908,27 +908,14 @@ static long madvise_populate(struct vm_area_struct *vma, {const bool write = behavior ==MADV_POPULATE_WRITE ;struct mm_struct *mm = vma->vm_mm; -unsigned long tmp_end;int locked =1 ;long pages; *prev = vma;while (start < end) { -/* -* We might have temporarily dropped the lock. For example, -* our VMA might have been split. -*/ -if (!vma || start >= vma->vm_end) { - vma =vma_lookup (mm, start); -if (!vma) -return -ENOMEM ; - } - - tmp_end = min_t(unsigned long, end, vma->vm_end);/* Populate (prefault) page tables readable/writable. */ - pages =faultin_vma_page_range (vma, start, tmp_end, write, - &locked); + pages =faultin_page_range (mm, start, end, write, &locked);if (!locked) {mmap_read_lock (mm); locked =1 ;
@@ -949,7 +936,7 @@ static long madvise_populate(struct vm_area_struct *vma,pr_warn_once ("%s: unhandled return value: %ld\n" , __func__, pages); fallthrough; -case -ENOMEM : +case -ENOMEM :/* No VMA or out of memory. */ return -ENOMEM ; } }
Signature · 1 line
2.43.2
PATCH 2/2 mm/madvise: don't perform madvise VMA walk for MADV_POPULATE_(READ|WRITE)
In reply to David HildenbrandWe changed faultin_page_range() to no longer consume a VMA, because faultin_page_range() might internally release the mm lock to lookup the VMA again -- required to cleanly handle VM_FAULT_RETRY. But independent of that, __get_user_pages() will always lookup the VMA itself.
Now that we let __get_user_pages() just handle VMA checks in a way that is suitable for MADV_POPULATE_(READ|WRITE), the VMA walk in madvise() is just overhead. So let's just call madvise_populate()
on the full range instead.
There is one change in behavior: madvise_walk_vmas() would skip any VMA holes, and if everything succeeded, it would return -ENOMEM after processing all VMAs.
However, for MADV_POPULATE_(READ|WRITE) it's unlikely for the caller to notice any difference: -ENOMEM might either indicate that there were VMA holes or that populating page tables failed because there was not enough memory. So it's unlikely that user space will notice the difference, and that special handling likely only makes sense for some other madvise() actions.
Further, we'd already fail with -ENOMEM early in the past if looking up the VMA after dropping the MM lock failed because of concurrent VMA modifications. So let's just keep it simple and avoid the madvise VMA walk, and consistently fail early if we find a VMA hole.
--- mm/madvise.c | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-)
mm/madvise.c +12 -14
@@ -901,26 +901,19 @@ static long madvise_dontneed_free(struct vm_area_struct *vma,return -EINVAL ; } -static long madvise_populate (struct vm_area_struct *vma, -struct vm_area_struct **prev, -unsigned long start,unsigned long end, -int behavior) +static long madvise_populate (struct mm_struct *mm,unsigned long start, +unsigned long end,int behavior) {const bool write = behavior ==MADV_POPULATE_WRITE ; -struct mm_struct *mm = vma->vm_mm;int locked =1 ;long pages; - *prev = vma; -while (start < end) {/* Populate (prefault) page tables readable/writable. */ pages =faultin_page_range (mm, start, end, write, &locked);if (!locked) {mmap_read_lock (mm); locked =1 ; - *prev =NULL ; - vma =NULL ; }if (pages <0 ) {switch (pages) {
@@ -1021,9 +1014,6 @@ static int madvise_vma_behavior(struct vm_area_struct *vma,case MADV_DONTNEED :case MADV_DONTNEED_LOCKED :return madvise_dontneed_free (vma, prev, start, end, behavior); -case MADV_POPULATE_READ : -case MADV_POPULATE_WRITE : -return madvise_populate (vma, prev, start, end, behavior);case MADV_NORMAL : new_flags = new_flags & ~VM_RAND_READ & ~VM_SEQ_READ ;break ;
@@ -1425,8 +1415,16 @@ int do_madvise(struct mm_struct *mm, unsigned long start, size_t len_in, int beh end = start + len;blk_start_plug (&plug); - error =madvise_walk_vmas (mm, start, end, behavior, - madvise_vma_behavior); +switch (behavior) { +case MADV_POPULATE_READ : +case MADV_POPULATE_WRITE : + error =madvise_populate (mm, start, end, behavior); +break ; +default : + error =madvise_walk_vmas (mm, start, end, behavior, + madvise_vma_behavior); +break ; + }blk_finish_plug (&plug);if (write)mmap_write_unlock (mm);
Signature · 1 line
2.43.2
Quoted 13 lines · David Hildenbrand
Derrick reports that in some cases where
pread()would fail with-EIOand mmap()+access would generate a SIGBUS signal,MADV_POPULATE_READ/MADV_POPULATE_WRITEwill keep retrying forever and not fail with-EFAULT.It all boils down to missing
VM_FAULT_RETRYhandling. Let's try to handle that in a better way, similar to how ordinary GUP handles it.Details in patch #1. In short, move special
MADV_POPULATE_(READ|WRITE)VMA handling into__get_user_pages(), and makefaultin_page_range()call__get_user_pages_locked(), which handlesVM_FAULT_RETRY. Further, avoid the now-useless madvise VMA walk, because__get_user_pages()will perform the VMA lookup either way.
Quoted 6 lines
I briefly played with handling the
FOLL_MADV_POPULATEchecks in__get_user_pages()a bit differently, integrating them with existing handling, but it ended up looking worse. So I decided to keep it simple.Likely, we need better selftests, but the reproducer from Darrick might be a bit hard to convert into a simple selftest.
No worries, I can convert my reproducer into an fstest. I actually had no idea that there were so many madvise flags, it's tempting to wire up fsx and fsstress so that the long soak group tests will exercise them.
Quoted 10 lines
Note that using
mlock()in Darricks reproducer results in a similar endless retry. Likely, that is not what we want, and we should handleVM_FAULT_RETRYinpopulate_vma_page_range()/__mm_populate()as well. However, similarly using__get_user_pages_locked()might be more complicated, because of the advanced VMA handling inpopulate_vma_page_range().Further, most
populate_vma_page_range()callers simply ignore the return values, so it's unclear in which cases we expect to just silently fail, or where we'd want to retry+fail or endlessly retry instead.
With this patchset applied, my reproducer no longer gets stuck in an infinite loop. I'll throw this at fstests overnight and see if anything else falls out. Thank you!
--D
Quoted 22 lines
Cc Andrew Morton <[email protected]>Cc Darrick J. Wong <[email protected]>Cc John Hubbard <[email protected]>Cc Jason Gunthorpe <[email protected]>Cc Hugh Dickins <[email protected]>David Hildenbrand (2):
mm/madvise: makeMADV_POPULATE_(READ|WRITE)handleVM_FAULT_RETRY
properly
mm/madvise: don't perform madvise VMA walk for
MADV_POPULATE_(READ|WRITE)mm/gup.c | 54 ++++++++++++++++++++++++++++++--------------------- mm/internal.h | 10 ++++++---- mm/madvise.c | 43 +++++++++++++--------------------------- 3 files changed, 52 insertions(+), 55 deletions(-)base-commit:
f48159f866f422371bb1aad10eb4d05b29ca4d8cSignature · 1 line
2.43.2
Quoted 31 lines · David Hildenbrand
Derrick reports that in some cases where
pread()would fail with-EIOand mmap()+access would generate a SIGBUS signal,MADV_POPULATE_READ/MADV_POPULATE_WRITEwill keep retrying forever and not fail with-EFAULT.It all boils down to missing
VM_FAULT_RETRYhandling. Let's try to handle that in a better way, similar to how ordinary GUP handles it.Details in patch #1. In short, move special
MADV_POPULATE_(READ|WRITE)VMA handling into__get_user_pages(), and makefaultin_page_range()call__get_user_pages_locked(), which handlesVM_FAULT_RETRY. Further, avoid the now-useless madvise VMA walk, because__get_user_pages()will perform the VMA lookup either way.I briefly played with handling the
FOLL_MADV_POPULATEchecks in__get_user_pages()a bit differently, integrating them with existing handling, but it ended up looking worse. So I decided to keep it simple.Likely, we need better selftests, but the reproducer from Darrick might be a bit hard to convert into a simple selftest.
Note that using
mlock()in Darricks reproducer results in a similar endless retry. Likely, that is not what we want, and we should handleVM_FAULT_RETRYinpopulate_vma_page_range()/__mm_populate()as well. However, similarly using__get_user_pages_locked()might be more complicated, because of the advanced VMA handling inpopulate_vma_page_range().Further, most
populate_vma_page_range()callers simply ignore the return values, so it's unclear in which cases we expect to just silently fail, or where we'd want to retry+fail or endlessly retry instead.
Quoted 5 lines
Cc Andrew Morton <[email protected]>Cc Darrick J. Wong <[email protected]>Cc John Hubbard <[email protected]>Cc Jason Gunthorpe <[email protected]>Cc Hugh Dickins <[email protected]>
After a few days I haven't seen any problems, so
--D
Quoted 17 lines
David Hildenbrand (2):
mm/madvise: makeMADV_POPULATE_(READ|WRITE)handleVM_FAULT_RETRY
properly
mm/madvise: don't perform madvise VMA walk for
MADV_POPULATE_(READ|WRITE)mm/gup.c | 54 ++++++++++++++++++++++++++++++--------------------- mm/internal.h | 10 ++++++---- mm/madvise.c | 43 +++++++++++++--------------------------- 3 files changed, 52 insertions(+), 55 deletions(-)base-commit:
f48159f866f422371bb1aad10eb4d05b29ca4d8cSignature · 1 line
2.43.2
RFC PATCH 1/1 xfs_io: add linux madvise advice codes
In reply to David HildenbrandFrom: Darrick J. Wong <[email protected]>
Add all the Linux-specific madvise codes. We're going to need MADV_POPULATE_READ for a regression test.
--- configure.ac | 1 include/builddefs.in | 1 io/Makefile | 4 ++ io/madvise.c | 111 +++++++++++++++++++++++++++++++++++++++++++++++++ m4/package_libcdev.m4 | 17 ++++++++ 5 files changed, 133 insertions(+), 1 deletion(-)
configure.ac +1 -0
@@ -187,6 +187,7 @@ AC_CONFIG_SYSTEMD_SYSTEM_UNIT_DIR AC_CONFIG_CROND_DIR AC_CONFIG_UDEV_DIR AC_HAVE_BLKID_TOPO +AC_HAVE_KERNEL_MADVISE_FLAGS if test "$enable_ubsan" = "yes" || test "$enable_ubsan" = "probe"; then AC_PACKAGE_CHECK_UBSAN
include/builddefs.in +1 -0
@@ -193,6 +193,7 @@ HAVE_O_TMPFILE = @have_o_tmpfile@ HAVE_MKOSTEMP_CLOEXEC = @have_mkostemp_cloexec@ USE_RADIX_TREE_FOR_INUMS = @use_radix_tree_for_inums@ HAVE_FSVERITY_DESCR = @have_fsverity_descr@ +HAVE_KERNEL_MADVISE = @have_kernel_madvise@ GCCFLAGS = -funsigned-char -fno-strict-aliasing -Wall -Werror -Wextra -Wno-unused-parameter # -Wbitwise -Wno-transparent-union -Wno-old-initializer -Wno-decl
io/Makefile +4 -0
@@ -84,6 +84,10 @@ ifeq ($(HAVE_GETFSMAP),yes) CFILES += fsmap.c endif +ifeq ($(HAVE_KERNEL_MADVISE),yes) +LCFLAGS += -DHAVE_KERNEL_MADVISE +endif + default: depend $(LTCOMMAND) include $(BUILDRULES)
io/madvise.c +110 -1
142 lines not on this page · raw message
m4/package_libcdev.m4 +17 -0
@@ -322,3 +322,20 @@ struct fsverity_descriptor m = { }; AC_SUBST(have_fsverity_descr) ]) +# +# Check if asm/mman.h can be included +# +AC_DEFUN([AC_HAVE_KERNEL_MADVISE_FLAGS], + [ AC_MSG_CHECKING([for kernel madvise flags in asm/mman.h ]) + AC_COMPILE_IFELSE( + [ AC_LANG_PROGRAM([[ +#include <asm/mman.h> + ]], [[ +int moo = MADV_COLLAPSE; + ]]) + ], have_kernel_madvise=yes + AC_MSG_RESULT(yes), + AC_MSG_RESULT(no)) + AC_SUBST(have_kernel_madvise) + ]) +
RFC PATCH 1/1 fstests: test MADV_POPULATE_READ with IO errors
From: Darrick J. Wong <[email protected]>
This is a regression test for "mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY properly".
--- tests/generic/1835 | 65 ++++++++++++++++++++++++++++++++++++++++++++++++ tests/generic/1835.out | 4 +++ 2 files changed, 69 insertions(+) create mode 100755 tests/generic/1835 create mode 100644 tests/generic/1835.out
tests/generic/1835 new file +65 -0
@@ -0,0 +1,65 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2024 Oracle. All Rights Reserved. +# +# FS QA Test 1835 +# +# This is a regression test for a kernel hang that I saw when creating a memory +# mapping, injecting EIO errors on the block device, and invoking +# MADV_POPULATE_READ on the mapping to fault in the pages. +# +. ./common/preamble +_begin_fstest auto rw + +# Override the default cleanup function. +_cleanup() +{ + cd / + rm -f $tmp.* + _dmerror_unmount + _dmerror_cleanup +} + +# Import common functions. +. ./common/dmerror + +_fixed_by_kernel_commit XXXXXXXXXXXX \ + "mm/madvise: make MADV_POPULATE_(READ|WRITE) handle VM_FAULT_RETRY properly" + +# real QA test starts here + +# Modify as appropriate. +_supported_fs generic +_require_xfs_io_command madvise -R +_require_scratch +_require_dm_target error +_require_command "$TIMEOUT_PROG" "timeout" + +_scratch_mkfs >> $seqres.full 2>&1 +_dmerror_init + +filesz=2m + +# Create a file that we'll read, then cycle mount to zap pagecache +_dmerror_mount +$XFS_IO_PROG -f -c "pwrite -S 0x58 0 $filesz" "$SCRATCH_MNT/a" >> $seqres.full +_dmerror_unmount +_dmerror_mount + +# Try to read the file data in a regular fashion just to prove that it works. +echo read with no errors +timeout -s KILL 10s $XFS_IO_PROG -c "mmap -r 0 $filesz" -c "madvise -R 0 $filesz" "$SCRATCH_MNT/a" +_dmerror_unmount +_dmerror_mount + +# Load file metadata and induce EIO errors on read. Try to provoke the kernel; +# kill the process after 10s so we can clean up. +stat "$SCRATCH_MNT/a" >> $seqres.full +echo read with IO errors +_dmerror_load_error_table +timeout -s KILL 10s $XFS_IO_PROG -c "mmap -r 0 $filesz" -c "madvise -R 0 $filesz" "$SCRATCH_MNT/a" +_dmerror_load_working_table + +# success, all done +status=0 +exit
tests/generic/1835.out new file +4 -0
@@ -0,0 +1,4 @@ +QA output created by 1835 +read with no errors +read with IO errors +madvise: Bad address
Re: [RFC PATCH] fstests: test MADV_POPULATE_READ with IO errors
Looks good:
Re: [RFC PATCH] fstests: test MADV_POPULATE_READ with IO errors
In reply to Darrick J. WongQuoted 8 lines · Darrick J. Wong
From: Darrick J. Wong <[email protected]>
This is a regression test for "mm/madvise: make
MADV_POPULATE_(READ|WRITE)handleVM_FAULT_RETRYproperly".Cc David Hildenbrand <[email protected]>Signed-off-by Darrick J. Wong <[email protected]>---
Thanks for including this test, very helpful!
It's my first time reading fstests code, so I cannot give any feedback that would be of a lot of value. Having that said, nothing jumped at me :)
Signature · 3 lines
Cheers, David / dhildenb
Re: [RFC PATCH] xfs_io: add linux madvise advice codes
In reply to Darrick J. WongQuoted 7 lines
m4/package_libcdev.m4 +7
-0+# +# Check if asm/mman.h can be included +# +AC_DEFUN([AC_HAVE_KERNEL_MADVISE_FLAGS], + [ AC_MSG_CHECKING([for kernel madvise flags in asm/mman.h ]) + AC_COMPILE_IFELSE( + [ AC_LANG_PROGRAM([[
m4/package_libcdev.m4 struct fsverity_descriptor m = { }; · line 341
Quoted 10 lines
m4/package_libcdev.m4 +10
-0+#include <asm/mman.h> + ]], [[ +int moo = MADV_COLLAPSE; + ]]) + ], have_kernel_madvise=yes + AC_MSG_RESULT(yes), + AC_MSG_RESULT(no)) + AC_SUBST(have_kernel_madvise) + ]) +
I don't think we really need this check, as madvise and asm/mman.h have been around forever. We can probably also drop most of the actual flag idefs, probably for everything older than MADV_WIPEONFORK.
The rest looks good to me.