Make core VMA operations internal and testable
Subsystems (8)
v4 cover Make core VMA operations internal and testable
There are a number of "core" VMA manipulation functions implemented in mm/mmap.c, notably those concerning VMA merging, splitting, modifying, expanding and shrinking, which logically don't belong there.
More importantly this functionality represents an internal implementation detail of memory management and should not be exposed outside of mm/ itself.
This patch series isolates core VMA manipulation functionality into its own file, mm/vma.c, and provides an API to the rest of the mm code in mm/vma.h.
Importantly, it also carefully implements mm/vma_internal.h, which specifies which headers need to be imported by vma.c, leading to the very useful property that vma.c depends only on mm/vma.h and mm/vma_internal.h.
This means we can then re-implement vma_internal.h in userland, adding shims for kernel mechanisms as required, allowing us to unit test internal VMA functionality.
This testing is useful as opposed to an e.g. kunit implementation as this way we can avoid all external kernel side-effects while testing, run tests VERY quickly, and iterate on and debug problems quickly.
Excitingly this opens the door to, in the future, recreating precise problems observed in production in userland and very quickly debugging problems that might otherwise be very difficult to reproduce.
This patch series takes advantage of existing shim logic and full userland maple tree support contained in tools/testing/radix-tree/ and tools/include/linux/, separating out shared components of the radix tree implementation to provide this testing.
Kernel functionality is stubbed and shimmed as needed in tools/testing/vma/ which contains a fully functional userland vma_internal.h file and which imports mm/vma.c and mm/vma.h to be directly tested from userland.
A simple, skeleton testing implementation is provided in tools/testing/vma/vma.c as a proof-of-concept, asserting that simple VMA merge, modify (testing split), expand and shrink functionality work correctly.
v4:
* Rebased on v6.11-rc1.
* Fixed radix-tree Makefile to build all targets.
* Cleaned up trivial issues with test make logic.
* Applied the 2 small fix patches from v3 - fix double header include and remove invalid asm/ header includes.
v3:
* Rebase on Linus's tree.
* Remove unnecessary use of extern keyword.
https://lore.kernel.org/all/[email protected]/
v2:
* NOMMU fixup in mm/vma.h.
* Fixup minor incorrect header edits and remove accidentally included empty test file, and incorrect license header.
* Remove generated/autoconf.h file from tools/testing/vma/ and create directory if doesn't already exist.
* Have vma binary return an error code if any tests fail.
https://lore.kernel.org/all/[email protected]/
v1:
* Fix test_simple_modify() to specify correct prev.
* Improve vma test Makefile so it picks up dependency changes correctly.
* Rename relocate_vma() to relocate_vma_down().
* Remove shift_arg_pages() and invoked relocate_vma_down() directly from setup_arg_pages().
* MAINTAINERS fixups.
https://lore.kernel.org/all/[email protected]/
RFC v2:
* Reword commit messages.
* Replace vma_expand() / vma_shrink() wrappers with relocate_vma().
* Make move_page_tables() internal too.
* Have internal.h import vma.h.
* Use header guards to more cleanly implement userland testing code.
* Rename main.c to vma.c.
* Update mm/vma_internal.h to have fewer superfluous comments.
* Rework testing logic so we count test failures, and output test results.
* Correct some SPDX license prefixes.
* Make VM_xxx_ON() debug asserts forward to xxx_ON() macros.
* Update VMA tests to correctly free memory, and re-enable ASAN leak detection.
https://lore.kernel.org/all/[email protected]/
RFC v1:
https://lore.kernel.org/all/[email protected]/
Lorenzo Stoakes (7):
userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
mm: move vma_modify() and helpers to internal header
mm: move vma_shrink(), vma_expand() to internal header
mm: move internal core VMA manipulation functions to own file
MAINTAINERS: Add entry for new VMA files
tools: separate out shared radix-tree components
tools: add skeleton code for userland testing of VMA logic
MAINTAINERS | 14 +
fs/exec.c | 81 +-
fs/userfaultfd.c | 160 +-
include/linux/mm.h | 112 +-
include/linux/userfaultfd_k.h | 19 +
mm/Makefile | 2 +-
mm/internal.h | 167 +-
mm/mmap.c | 2069 ++---------------
mm/mmu_notifier.c | 2 +
mm/userfaultfd.c | 168 ++
mm/vma.c | 1766 ++++++++++++++
mm/vma.h | 364 +++
mm/vma_internal.h | 50 +
tools/testing/radix-tree/.gitignore | 1 +
tools/testing/radix-tree/Makefile | 72 +-
tools/testing/radix-tree/xarray.c | 10 +-
.../generated => shared}/autoconf.h | 0
tools/testing/{radix-tree => shared}/linux.c | 0
.../{radix-tree => shared}/linux/bug.h | 0
.../{radix-tree => shared}/linux/cpu.h | 0
.../{radix-tree => shared}/linux/idr.h | 0
.../{radix-tree => shared}/linux/init.h | 0
.../{radix-tree => shared}/linux/kconfig.h | 0
.../{radix-tree => shared}/linux/kernel.h | 0
.../{radix-tree => shared}/linux/kmemleak.h | 0
.../{radix-tree => shared}/linux/local_lock.h | 0
.../{radix-tree => shared}/linux/lockdep.h | 0
.../{radix-tree => shared}/linux/maple_tree.h | 0
.../{radix-tree => shared}/linux/percpu.h | 0
.../{radix-tree => shared}/linux/preempt.h | 0
.../{radix-tree => shared}/linux/radix-tree.h | 0
.../{radix-tree => shared}/linux/rcupdate.h | 0
.../{radix-tree => shared}/linux/xarray.h | 0
tools/testing/shared/maple-shared.h | 9 +
tools/testing/shared/maple-shim.c | 7 +
tools/testing/shared/shared.h | 33 +
tools/testing/shared/shared.mk | 72 +
.../trace/events/maple_tree.h | 0
tools/testing/shared/xarray-shared.c | 5 +
tools/testing/shared/xarray-shared.h | 4 +
tools/testing/vma/.gitignore | 7 +
tools/testing/vma/Makefile | 16 +
tools/testing/vma/linux/atomic.h | 12 +
tools/testing/vma/linux/mmzone.h | 38 +
tools/testing/vma/vma.c | 207 ++
tools/testing/vma/vma_internal.h | 882 +++++++
46 files changed, 3907 insertions(+), 2442 deletions(-)
create mode 100644 mm/vma.c
create mode 100644 mm/vma.h
create mode 100644 mm/vma_internal.h
rename tools/testing/{radix-tree/generated => shared}/autoconf.h (100%)
rename tools/testing/{radix-tree => shared}/linux.c (100%)
rename tools/testing/{radix-tree => shared}/linux/bug.h (100%)
rename tools/testing/{radix-tree => shared}/linux/cpu.h (100%)
rename tools/testing/{radix-tree => shared}/linux/idr.h (100%)
rename tools/testing/{radix-tree => shared}/linux/init.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kconfig.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kernel.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kmemleak.h (100%)
rename tools/testing/{radix-tree => shared}/linux/local_lock.h (100%)
rename tools/testing/{radix-tree => shared}/linux/lockdep.h (100%)
rename tools/testing/{radix-tree => shared}/linux/maple_tree.h (100%)
rename tools/testing/{radix-tree => shared}/linux/percpu.h (100%)
rename tools/testing/{radix-tree => shared}/linux/preempt.h (100%)
rename tools/testing/{radix-tree => shared}/linux/radix-tree.h (100%)
rename tools/testing/{radix-tree => shared}/linux/rcupdate.h (100%)
rename tools/testing/{radix-tree => shared}/linux/xarray.h (100%)
create mode 100644 tools/testing/shared/maple-shared.h
create mode 100644 tools/testing/shared/maple-shim.c
create mode 100644 tools/testing/shared/shared.h
create mode 100644 tools/testing/shared/shared.mk
rename tools/testing/{radix-tree => shared}/trace/events/maple_tree.h (100%)
create mode 100644 tools/testing/shared/xarray-shared.c
create mode 100644 tools/testing/shared/xarray-shared.h
create mode 100644 tools/testing/vma/.gitignore
create mode 100644 tools/testing/vma/Makefile
create mode 100644 tools/testing/vma/linux/atomic.h
create mode 100644 tools/testing/vma/linux/mmzone.h
create mode 100644 tools/testing/vma/vma.c
create mode 100644 tools/testing/vma/vma_internal.h--
2.45.2
PATCH v4 1/7 userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
This patch forms part of a patch series intending to separate out VMA logic and render it testable from userspace, which requires that core manipulation functions be exposed in an mm/-internal header file.
In order to do this, we must abstract APIs we wish to test, in this instance functions which ultimately invoke vma_modify().
This patch therefore moves all logic which ultimately invokes vma_modify() to mm/userfaultfd.c, trying to transfer code at a functional granularity where possible.
--- fs/userfaultfd.c | 160 +++----------------------------- include/linux/userfaultfd_k.h | 19 ++++ mm/userfaultfd.c | 168 ++++++++++++++++++++++++++++++++++ 3 files changed, 198 insertions(+), 149 deletions(-)
fs/userfaultfd.c +11 -149
@@ -104,21 +104,6 @@ bool userfaultfd_wp_unpopulated(struct vm_area_struct *vma)return ctx->features &UFFD_FEATURE_WP_UNPOPULATED ; } -static void userfaultfd_set_vm_flags (struct vm_area_struct *vma, -vm_flags_t flags) -{ -const bool uffd_wp_changed = (vma->vm_flags ^ flags) &VM_UFFD_WP ; - -vm_flags_reset (vma, flags); -/* -* For shared mappings, we want to enable writenotify while -* userfaultfd-wp is enabled (see vma_wants_writenotify()). We'll simply -* recalculate vma->vm_page_prot whenever userfaultfd-wp changes. -*/ -if ((vma->vm_flags &VM_SHARED ) && uffd_wp_changed) -vma_set_page_prot (vma); -} -static int userfaultfd_wake_function (wait_queue_entry_t *wq,unsigned mode,int wake_flags,void *key) {
@@ -615,22 +600,7 @@ static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,spin_unlock_irq (&ctx->event_wqh.lock);if (release_new_ctx) { -struct vm_area_struct *vma; -struct mm_struct *mm = release_new_ctx->mm; -VMA_ITERATOR (vmi, mm,0 ); - -/* the various vma->vm_userfaultfd_ctx still points to it */ -mmap_write_lock (mm); -for_each_vma (vmi, vma) { -if (vma->vm_userfaultfd_ctx.ctx == release_new_ctx) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, - vma->vm_flags & ~__VM_UFFD_FLAGS); - } - } -mmap_write_unlock (mm); - +userfaultfd_release_new (release_new_ctx);userfaultfd_ctx_put (release_new_ctx); }
@@ -662,9 +632,7 @@ int dup_userfaultfd(struct vm_area_struct *vma, struct list_head *fcs)return 0 ;if (!(octx->features &UFFD_FEATURE_EVENT_FORK )) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma);return 0 ; }
@@ -749,9 +717,7 @@ void mremap_userfaultfd_prep(struct vm_area_struct *vma,up_write (&ctx->map_changing_lock); }else {/* Drop uffd context if remap feature not enabled */ -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma); } }
@@ -870,53 +836,13 @@ static int userfaultfd_release(struct inode *inode, struct file *file) {struct userfaultfd_ctx *ctx = file->private_data;struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev;/* len == 0 means wake all */ struct userfaultfd_wake_range range = { .len =0 , }; -unsigned long new_flags; -VMA_ITERATOR (vmi, mm,0 );WRITE_ONCE (ctx->released, true); -if (!mmget_not_zero (mm)) - goto wakeup; - -/* -* Flush page faults out of all CPUs. NOTE: all page faults -* must be retried without returning VM_FAULT_SIGBUS if -* userfaultfd_ctx_get() succeeds but vma->vma_userfault_ctx -* changes while handle_userfault released the mmap_lock. So -* it's critical that released is set to true (above), before -* taking the mmap_lock for writing. -*/ -mmap_write_lock (mm); - prev =NULL ; -for_each_vma (vmi, vma) { -cond_resched (); -BUG_ON (!!vma->vm_userfaultfd_ctx.ctx ^ - !!(vma->vm_flags & __VM_UFFD_FLAGS)); -if (vma->vm_userfaultfd_ctx.ctx != ctx) { - prev = vma; -continue ; - } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, vma->vm_start, - vma->vm_end - vma->vm_start, false); - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, vma->vm_start, - vma->vm_end, new_flags, -NULL_VM_UFFD_CTX ); - -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; +userfaultfd_release_all (mm, ctx); - prev = vma; - } -mmap_write_unlock (mm); -mmput (mm); -wakeup:/* * After no new page faults can wait on this fault_*wqh, flush * the last page faults that may have been already waiting on
@@ -1293,14 +1219,14 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, unsigned long arg) {struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev, *cur; +struct vm_area_struct *vma, *cur;int ret;struct uffdio_register uffdio_register;struct uffdio_register __user *user_uffdio_register; -unsigned long vm_flags, new_flags; +unsigned long vm_flags;bool found;bool basic_ioctls; -unsigned long start, end, vma_end; +unsigned long start, end;struct vma_iterator vmi;bool wp_async =userfaultfd_wp_async_ctx (ctx);
@@ -1428,57 +1354,8 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, }for_each_vma_range (vmi, cur, end);BUG_ON (!found); -vma_iter_set (&vmi, start); - prev =vma_prev (&vmi); -if (vma->vm_start < start) - prev = vma; - - ret =0 ; -for_each_vma_range (vmi, vma, end) { -cond_resched (); - -BUG_ON (!vma_can_userfault (vma, vm_flags, wp_async)); -BUG_ON (vma->vm_userfaultfd_ctx.ctx && - vma->vm_userfaultfd_ctx.ctx != ctx); -WARN_ON (!(vma->vm_flags &VM_MAYWRITE )); - -/* -* Nothing to do: this vma is already registered into this -* userfaultfd and with the right tracking mode too. -*/ -if (vma->vm_userfaultfd_ctx.ctx == ctx && - (vma->vm_flags & vm_flags) == vm_flags) - goto skip; - -if (vma->vm_start > start) - start = vma->vm_start; - vma_end =min (end, vma->vm_end); - - new_flags = (vma->vm_flags & ~__VM_UFFD_FLAGS) | vm_flags; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags, - (struct vm_userfaultfd_ctx ){ctx}); -if (IS_ERR (vma)) { - ret =PTR_ERR (vma); -break ; - } - -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx.ctx = ctx; - -if (is_vm_hugetlb_page (vma) &&uffd_disable_huge_pmd_share (vma)) -hugetlb_unshare_all_pmds (vma); - - skip: - prev = vma; - start = vma->vm_end; - } + ret =userfaultfd_register_range (ctx, vma, vm_flags, start, end, + wp_async); out_unlock:mmap_write_unlock (mm);
@@ -1519,7 +1396,6 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,struct vm_area_struct *vma, *prev, *cur;int ret;struct uffdio_range uffdio_unregister; -unsigned long new_flags;bool found;unsigned long start, end, vma_end;const void __user *buf = (void __user *)arg;
@@ -1622,27 +1498,13 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,wake_userfault (vma->vm_userfaultfd_ctx.ctx, &range); } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, start, vma_end - start, false); - - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags,NULL_VM_UFFD_CTX ); + vma =userfaultfd_clear_vma (&vmi, prev, vma, + start, vma_end);if (IS_ERR (vma)) { ret =PTR_ERR (vma);break ; } -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; - skip: prev = vma; start = vma->vm_end;
include/linux/userfaultfd_k.h +19 -0
@@ -267,6 +267,25 @@ extern void userfaultfd_unmap_complete(struct mm_struct *mm,extern bool userfaultfd_wp_unpopulated (struct vm_area_struct *vma);extern bool userfaultfd_wp_async (struct vm_area_struct *vma); +void userfaultfd_reset_ctx (struct vm_area_struct *vma); + +struct vm_area_struct *userfaultfd_clear_vma (struct vma_iterator *vmi, +struct vm_area_struct *prev, +struct vm_area_struct *vma, +unsigned long start, +unsigned long end); + +int userfaultfd_register_range (struct userfaultfd_ctx *ctx, +struct vm_area_struct *vma, +unsigned long vm_flags, +unsigned long start,unsigned long end, +bool wp_async); + +void userfaultfd_release_new (struct userfaultfd_ctx *ctx); + +void userfaultfd_release_all (struct mm_struct *mm, +struct userfaultfd_ctx *ctx); +#else /* CONFIG_USERFAULTFD */ /* mm helpers */
mm/userfaultfd.c +168 -0
171 lines not on this page · raw message
Signature · 1 line
2.45.2
Re: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.
Bisected the first bad commit:4651ba8201cf userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
All detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ctx
Syzkaller repro code: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.c
Syzkaller repro syscall steps: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.prog
Syzkaller analysis report: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.report
Kconfig(make olddefconfig): https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/kconfig_origin
Bisect info: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/bisect_info.log
Dmesg: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/d6dbc9f56c3a70e915625b6f1887882c23dc5c91_dmesg.log
bzImage: https://github.com/xupengfe/syzkaller_logs/raw/main/240806_122723_userfaultfd_set_ctx/bzImage_d6dbc9f56c3a70e915625b6f1887882c23dc5c91.tar.gz
"
[ 29.675551] ================================================================== [ 29.676133] BUG: KASAN: slab-use-after-free in userfaultfd_set_ctx+0x31c/0x360 [ 29.676716] Read of size 8 at addr ffff888027c5f100 by task repro/1498 [ 29.677218] [ 29.677358] CPU: 0 UID: 0 PID: 1498 Comm: repro Not tainted 6.11.0-rc2-next-20240805-d6dbc9f56c3a #1 [ 29.678053] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 [ 29.678910] Call Trace: [ 29.679117] <TASK> [ 29.679296] dump_stack_lvl+0xea/0x150 [ 29.679622] print_report+0xce/0x610 [ 29.679924] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.680289] ? kasan_complete_mode_report_info+0x80/0x200 [ 29.680716] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.681077] kasan_report+0xcc/0x110 [ 29.681372] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.681729] __asan_report_load8_noabort+0x18/0x20 [ 29.682118] userfaultfd_set_ctx+0x31c/0x360 [ 29.682465] userfaultfd_clear_vma+0x104/0x190 [ 29.682826] userfaultfd_release_all+0x294/0x4a0 [ 29.683201] ? __pfx_userfaultfd_release_all+0x10/0x10 [ 29.683615] ? __this_cpu_preempt_check+0x21/0x30 [ 29.684003] ? __pfx_userfaultfd_release+0x10/0x10 [ 29.684389] userfaultfd_release+0x112/0x1e0 [ 29.684735] ? __pfx_userfaultfd_release+0x10/0x10 [ 29.685114] ? evm_file_release+0x193/0x1f0 [ 29.685454] __fput+0x426/0xbc0 [ 29.685719] ? __sanitizer_cov_trace_const_cmp2+0x1c/0x30 [ 29.686153] __fput_sync+0x58/0x70 [ 29.686435] __x64_sys_close+0x93/0x120 [ 29.686744] x64_sys_call+0x189a/0x20d0 [ 29.687066] do_syscall_64+0x6d/0x140 [ 29.687371] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.687779] RIP: 0033:0x7f3b67b3f247 [ 29.688078] Code: ff e8 cd e3 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 c3 c9 f5 ff [ 29.689519] RSP: 002b:00007ffd1f0ac7d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003 [ 29.690140] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3b67b3f247 [ 29.690717] RDX: 0000000020000100 RSI: 000000008010aa01 RDI: 0000000000000003 [ 29.691270] RBP: 00007ffd1f0ac7f0 R08: 00007ffd1f0ac7f0 R09: 00007ffd1f0ac7f0 [ 29.691822] R10: 00007ffd1f0ac7f0 R11: 0000000000000246 R12: 00007ffd1f0ac968 [ 29.692375] R13: 0000000000401bf9 R14: 0000000000403e08 R15: 00007f3b67c72000 [ 29.692939] </TASK> [ 29.693124] [ 29.693258] Allocated by task 1498: [ 29.693545] kasan_save_stack+0x2c/0x60 [ 29.693875] kasan_save_track+0x18/0x40 [ 29.694205] kasan_save_alloc_info+0x3c/0x50 [ 29.694576] __kasan_slab_alloc+0x62/0x80 [ 29.694921] kmem_cache_alloc_noprof+0x114/0x370 [ 29.695319] vm_area_dup+0x2a/0x1b0 [ 29.695630] __split_vma+0x188/0x1020 [ 29.695952] vma_modify+0x1fc/0x390 [ 29.696250] userfaultfd_clear_vma+0xd4/0x190 [ 29.696609] userfaultfd_ioctl+0x3c0b/0x4560 [ 29.696964] __x64_sys_ioctl+0x1b9/0x230 [ 29.697295] x64_sys_call+0x1209/0x20d0 [ 29.697620] do_syscall_64+0x6d/0x140 [ 29.697937] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.698364] [ 29.698508] Freed by task 1505: [ 29.698779] kasan_save_stack+0x2c/0x60 [ 29.699110] kasan_save_track+0x18/0x40 [ 29.699441] kasan_save_free_info+0x3f/0x60 [ 29.699797] __kasan_slab_free+0x47/0x60 [ 29.700137] kmem_cache_free+0x2f2/0x4b0 [ 29.700471] vm_area_free_rcu_cb+0x7f/0xa0 [ 29.700819] rcu_core+0x877/0x18f0 [ 29.701123] rcu_core_si+0x12/0x20 [ 29.701421] handle_softirqs+0x1c7/0x870 [ 29.701760] __irq_exit_rcu+0xa9/0x120 [ 29.702082] irq_exit_rcu+0x12/0x30 [ 29.702386] sysvec_apic_timer_interrupt+0xa5/0xc0 [ 29.702802] asm_sysvec_apic_timer_interrupt+0x1f/0x30 [ 29.703237] [ 29.703377] Last potentially related work creation: [ 29.703782] kasan_save_stack+0x2c/0x60 [ 29.704114] __kasan_record_aux_stack+0x93/0xb0 [ 29.704503] kasan_record_aux_stack_noalloc+0xf/0x20 [ 29.704923] __call_rcu_common.constprop.0+0x72/0x6b0 [ 29.705349] call_rcu+0x12/0x20 [ 29.705625] vm_area_free+0x26/0x30 [ 29.705928] vma_complete+0x57e/0xf60 [ 29.706245] vma_merge+0x166b/0x3540 [ 29.706555] vma_modify+0x9f/0x390 [ 29.706853] userfaultfd_clear_vma+0xd4/0x190 [ 29.707227] userfaultfd_release_all+0x294/0x4a0 [ 29.707621] userfaultfd_release+0x112/0x1e0 [ 29.707991] __fput+0x426/0xbc0 [ 29.708267] __fput_sync+0x58/0x70 [ 29.708563] __x64_sys_close+0x93/0x120 [ 29.708891] x64_sys_call+0x189a/0x20d0 [ 29.709220] do_syscall_64+0x6d/0x140 [ 29.709538] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.709965] [ 29.710105] The buggy address belongs to the object at ffff888027c5f0f0 [ 29.710105] which belongs to the cache vm_area_struct of size 176 [ 29.711130] The buggy address is located 16 bytes inside of [ 29.711130] freed 176-byte region [ffff888027c5f0f0, ffff888027c5f1a0) [ 29.712104] [ 29.712245] The buggy address belongs to the physical page: [ 29.712703] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x27c5f [ 29.713349] memcg:ffff8880198eaa01 [ 29.713639] flags: 0xfffffc0000000(node=0|zone=1|lastcpupid=0x1fffff) [ 29.714173] page_type: 0xfdffffff(slab) [ 29.714507] raw: 000fffffc0000000 ffff88800d319dc0 dead000000000122 0000000000000000 [ 29.715137] raw: 0000000000000000 0000000000110011 00000001fdffffff ffff8880198eaa01 [ 29.715765] page dumped because: kasan: bad access detected [ 29.716220] [ 29.716360] Memory state around the buggy address: [ 29.716756] ffff888027c5f000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 29.717349] ffff888027c5f080: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fa fb [ 29.717940] >ffff888027c5f100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 29.718521] ^ [ 29.718796] ffff888027c5f180: fb fb fb fb fc fc fc fc fc fc fc fc 00 00 00 00 [ 29.719388] ffff888027c5f200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 29.720025] ================================================================== [ 29.720671] Disabling lock debugging due to kernel taint
"
Thanks!
---
If you don't need the following environment to reproduce the problem or if you already have one reproduced environment, please ignore the following information.
How to reproduce:
git clone https://gitlab.com/xupengfe/repro_vm_env.git
cd repro_vm_env
tar -xvf repro_vm_env.tar.gz
cd repro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
// start3.sh will load bzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65 v6.2-rc5 kernel
// You could change the bzImage_xxx as you want
// Maybe you need to remove line "-drive if=pflash,format=raw,readonly=on,file=./OVMF_CODE.fd \" for different qemu version
You could use below command to log in, there is no password for root.
ssh -p 10023 root@localhost
After login vm(virtual machine) successfully, you could transfer reproduced binary to the vm by below way, and reproduce the problem in vm:
gcc -pthread -o repro repro.c
scp -P 10023 repro root@localhost:/root/
Get the bzImage for target kernel:
Please use target kconfig and copy it to kernel_src/.config make olddefconfig
make -jx bzImage //x should equal or less than cpu num your pc has
Fill the bzImage file into above start3.sh to load the target kernel in vm.
Tips:
If you already have qemu-system-x86_64, please ignore below info.
If you want to install qemu v7.1.0 version:
git clone https://github.com/qemu/qemu.git
cd qemu
git checkout -f v7.1.0
mkdir build
cd build
yum install -y ninja-build.x86_64
yum -y install libslirp-devel.x86_64
../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl --enable-usb-redir --enable-slirp make
make install
Best Regards,
Thanks!
Quoted 472 lines · Lorenzo Stoakes
This patch forms part of a patch series intending to separate out VMA logic and render it testable from userspace, which requires that core manipulation functions be exposed in an
mm/-internalheader file.In order to do this, we must abstract APIs we wish to test, in this instance functions which ultimately invoke
vma_modify().This patch therefore moves all logic which ultimately invokes
vma_modify()tomm/userfaultfd.c, trying to transfer code at a functional granularity where possible.Reviewed-by Vlastimil Babka <[email protected]>Reviewed-by Liam R. Howlett <[email protected]>Signed-off-by Lorenzo Stoakes <[email protected]>--- fs/userfaultfd.c | 160 +++----------------------------- include/linux/userfaultfd_k.h | 19 ++++ mm/userfaultfd.c | 168 ++++++++++++++++++++++++++++++++++ 3 files changed, 198 insertions(+), 149 deletions(-)fs/userfaultfd.c +11
-149@@ -104,21 +104,6 @@ bool userfaultfd_wp_unpopulated(struct vm_area_struct *vma)return ctx->features &UFFD_FEATURE_WP_UNPOPULATED ; } -static void userfaultfd_set_vm_flags (struct vm_area_struct *vma, -vm_flags_t flags) -{ -const bool uffd_wp_changed = (vma->vm_flags ^ flags) &VM_UFFD_WP ; - -vm_flags_reset (vma, flags); -/* -* For shared mappings, we want to enable writenotify while -* userfaultfd-wp is enabled (see vma_wants_writenotify()). We'll simply -* recalculate vma->vm_page_prot whenever userfaultfd-wp changes. -*/ -if ((vma->vm_flags &VM_SHARED ) && uffd_wp_changed) -vma_set_page_prot (vma); -} -static int userfaultfd_wake_function (wait_queue_entry_t *wq,unsigned mode,int wake_flags,void *key) {@@ -615,22 +600,7 @@ static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,spin_unlock_irq (&ctx->event_wqh.lock);if (release_new_ctx) { -struct vm_area_struct *vma; -struct mm_struct *mm = release_new_ctx->mm; -VMA_ITERATOR (vmi, mm,0 ); - -/* the various vma->vm_userfaultfd_ctx still points to it */ -mmap_write_lock (mm); -for_each_vma (vmi, vma) { -if (vma->vm_userfaultfd_ctx.ctx == release_new_ctx) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, - vma->vm_flags & ~__VM_UFFD_FLAGS); - } - } -mmap_write_unlock (mm); - +userfaultfd_release_new (release_new_ctx);userfaultfd_ctx_put (release_new_ctx); }@@ -662,9 +632,7 @@ int dup_userfaultfd(struct vm_area_struct *vma, struct list_head *fcs)return 0 ;if (!(octx->features &UFFD_FEATURE_EVENT_FORK )) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma);return 0 ; }@@ -749,9 +717,7 @@ void mremap_userfaultfd_prep(struct vm_area_struct *vma,up_write (&ctx->map_changing_lock); }else {/* Drop uffd context if remap feature not enabled */ -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma); } }@@ -870,53 +836,13 @@ static int userfaultfd_release(struct inode *inode, struct file *file) {struct userfaultfd_ctx *ctx = file->private_data;struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev;/* len == 0 means wake all */ struct userfaultfd_wake_range range = { .len =0 , }; -unsigned long new_flags; -VMA_ITERATOR (vmi, mm,0 );WRITE_ONCE (ctx->released, true); -if (!mmget_not_zero (mm)) - goto wakeup; - -/* -* Flush page faults out of all CPUs. NOTE: all page faults -* must be retried without returning VM_FAULT_SIGBUS if -* userfaultfd_ctx_get() succeeds but vma->vma_userfault_ctx -* changes while handle_userfault released the mmap_lock. So -* it's critical that released is set to true (above), before -* taking the mmap_lock for writing. -*/ -mmap_write_lock (mm); - prev =NULL ; -for_each_vma (vmi, vma) { -cond_resched (); -BUG_ON (!!vma->vm_userfaultfd_ctx.ctx ^ - !!(vma->vm_flags & __VM_UFFD_FLAGS)); -if (vma->vm_userfaultfd_ctx.ctx != ctx) { - prev = vma; -continue ; - } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, vma->vm_start, - vma->vm_end - vma->vm_start, false); - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, vma->vm_start, - vma->vm_end, new_flags, -NULL_VM_UFFD_CTX ); - -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; +userfaultfd_release_all (mm, ctx); - prev = vma; - } -mmap_write_unlock (mm); -mmput (mm); -wakeup:/* * After no new page faults can wait on this fault_*wqh, flush * the last page faults that may have been already waiting on @@ -1293,14 +1219,14 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, unsigned long arg) {struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev, *cur; +struct vm_area_struct *vma, *cur;int ret;struct uffdio_register uffdio_register;struct uffdio_register __user *user_uffdio_register; -unsigned long vm_flags, new_flags; +unsigned long vm_flags;bool found;bool basic_ioctls; -unsigned long start, end, vma_end; +unsigned long start, end;struct vma_iterator vmi;bool wp_async =userfaultfd_wp_async_ctx (ctx);@@ -1428,57 +1354,8 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, }for_each_vma_range (vmi, cur, end);BUG_ON (!found); -vma_iter_set (&vmi, start); - prev =vma_prev (&vmi); -if (vma->vm_start < start) - prev = vma; - - ret =0 ; -for_each_vma_range (vmi, vma, end) { -cond_resched (); - -BUG_ON (!vma_can_userfault (vma, vm_flags, wp_async)); -BUG_ON (vma->vm_userfaultfd_ctx.ctx && - vma->vm_userfaultfd_ctx.ctx != ctx); -WARN_ON (!(vma->vm_flags &VM_MAYWRITE )); - -/* -* Nothing to do: this vma is already registered into this -* userfaultfd and with the right tracking mode too. -*/ -if (vma->vm_userfaultfd_ctx.ctx == ctx && - (vma->vm_flags & vm_flags) == vm_flags) - goto skip; - -if (vma->vm_start > start) - start = vma->vm_start; - vma_end =min (end, vma->vm_end); - - new_flags = (vma->vm_flags & ~__VM_UFFD_FLAGS) | vm_flags; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags, - (struct vm_userfaultfd_ctx ){ctx}); -if (IS_ERR (vma)) { - ret =PTR_ERR (vma); -break ; - } - -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx.ctx = ctx; - -if (is_vm_hugetlb_page (vma) &&uffd_disable_huge_pmd_share (vma)) -hugetlb_unshare_all_pmds (vma); - - skip: - prev = vma; - start = vma->vm_end; - } + ret =userfaultfd_register_range (ctx, vma, vm_flags, start, end, + wp_async); out_unlock:mmap_write_unlock (mm);@@ -1519,7 +1396,6 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,struct vm_area_struct *vma, *prev, *cur;int ret;struct uffdio_range uffdio_unregister; -unsigned long new_flags;bool found;unsigned long start, end, vma_end;const void __user *buf = (void __user *)arg;@@ -1622,27 +1498,13 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,wake_userfault (vma->vm_userfaultfd_ctx.ctx, &range); } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, start, vma_end - start, false); - - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags,NULL_VM_UFFD_CTX ); + vma =userfaultfd_clear_vma (&vmi, prev, vma, + start, vma_end);if (IS_ERR (vma)) { ret =PTR_ERR (vma);break ; } -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; - skip: prev = vma; start = vma->vm_end;include/linux/userfaultfd_k.h +19
-0@@ -267,6 +267,25 @@ extern void userfaultfd_unmap_complete(struct mm_struct *mm,extern bool userfaultfd_wp_unpopulated (struct vm_area_struct *vma);extern bool userfaultfd_wp_async (struct vm_area_struct *vma); +void userfaultfd_reset_ctx (struct vm_area_struct *vma); + +struct vm_area_struct *userfaultfd_clear_vma (struct vma_iterator *vmi, +struct vm_area_struct *prev, +struct vm_area_struct *vma, +unsigned long start, +unsigned long end); + +int userfaultfd_register_range (struct userfaultfd_ctx *ctx, +struct vm_area_struct *vma, +unsigned long vm_flags, +unsigned long start,unsigned long end, +bool wp_async); + +void userfaultfd_release_new (struct userfaultfd_ctx *ctx); + +void userfaultfd_release_all (struct mm_struct *mm, +struct userfaultfd_ctx *ctx); +#else /* CONFIG_USERFAULTFD */ /* mm helpers */ mm/userfaultfd.c +168
-0@@ -1760,3 +1760,171 @@ ssize_t move_pages(struct userfaultfd_ctx *ctx, unsigned long dst_start,VM_WARN_ON (!moved && !err);return moved ? moved : err; } + +static void userfaultfd_set_vm_flags (struct vm_area_struct *vma, +vm_flags_t flags) +{ +const bool uffd_wp_changed = (vma->vm_flags ^ flags) &VM_UFFD_WP ; + +vm_flags_reset (vma, flags); +/* +* For shared mappings, we want to enable writenotify while +* userfaultfd-wp is enabled (see vma_wants_writenotify()). We'll simply +* recalculate vma->vm_page_prot whenever userfaultfd-wp changes. +*/ +if ((vma->vm_flags &VM_SHARED ) && uffd_wp_changed) +vma_set_page_prot (vma); +} + +static void userfaultfd_set_ctx (struct vm_area_struct *vma, +struct userfaultfd_ctx *ctx, +unsigned long flags) +{ +vma_start_write (vma); + vma->vm_userfaultfd_ctx = (struct vm_userfaultfd_ctx ){ctx}; +userfaultfd_set_vm_flags (vma, + (vma->vm_flags & ~__VM_UFFD_FLAGS) | flags); +} + +void userfaultfd_reset_ctx (struct vm_area_struct *vma) +{ +userfaultfd_set_ctx (vma,NULL ,0 ); +} + +struct vm_area_struct *userfaultfd_clear_vma (struct vma_iterator *vmi, +struct vm_area_struct *prev, +struct vm_area_struct *vma, +unsigned long start, +unsigned long end) +{ +struct vm_area_struct *ret; + +/* Reset ptes for the whole vma range if wr-protected */ +if (userfaultfd_wp (vma)) +uffd_wp_range (vma, start, end - start, false); + + ret =vma_modify_flags_uffd (vmi, prev, vma, start, end, + vma->vm_flags & ~__VM_UFFD_FLAGS, +NULL_VM_UFFD_CTX ); + +/* +* In the vma_merge() successful mprotect-like case 8: +* the next vma was merged into the current one and +* the current one has not been updated yet. +*/ +if (!IS_ERR (ret)) +userfaultfd_reset_ctx (vma); + +return ret; +} + +/* Assumes mmap write lock taken, and mm_struct pinned. */ +int userfaultfd_register_range (struct userfaultfd_ctx *ctx, +struct vm_area_struct *vma, +unsigned long vm_flags, +unsigned long start,unsigned long end, +bool wp_async) +{ +VMA_ITERATOR (vmi, ctx->mm, start); +struct vm_area_struct *prev =vma_prev (&vmi); +unsigned long vma_end; +unsigned long new_flags; + +if (vma->vm_start < start) + prev = vma; + +for_each_vma_range (vmi, vma, end) { +cond_resched (); + +BUG_ON (!vma_can_userfault (vma, vm_flags, wp_async)); +BUG_ON (vma->vm_userfaultfd_ctx.ctx && + vma->vm_userfaultfd_ctx.ctx != ctx); +WARN_ON (!(vma->vm_flags &VM_MAYWRITE )); + +/* +* Nothing to do: this vma is already registered into this +* userfaultfd and with the right tracking mode too. +*/ +if (vma->vm_userfaultfd_ctx.ctx == ctx && + (vma->vm_flags & vm_flags) == vm_flags) + goto skip; + +if (vma->vm_start > start) + start = vma->vm_start; + vma_end =min (end, vma->vm_end); + + new_flags = (vma->vm_flags & ~__VM_UFFD_FLAGS) | vm_flags; + vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, + new_flags, + (struct vm_userfaultfd_ctx ){ctx}); +if (IS_ERR (vma)) +return PTR_ERR (vma); + +/* +* In the vma_merge() successful mprotect-like case 8: +* the next vma was merged into the current one and +* the current one has not been updated yet. +*/ +userfaultfd_set_ctx (vma, ctx, vm_flags); + +if (is_vm_hugetlb_page (vma) &&uffd_disable_huge_pmd_share (vma)) +hugetlb_unshare_all_pmds (vma); + +skip: + prev = vma; + start = vma->vm_end; + } + +return 0 ; +} + +void userfaultfd_release_new (struct userfaultfd_ctx *ctx) +{ +struct mm_struct *mm = ctx->mm; +struct vm_area_struct *vma; +VMA_ITERATOR (vmi, mm,0 ); + +/* the various vma->vm_userfaultfd_ctx still points to it */ +mmap_write_lock (mm); +for_each_vma (vmi, vma) { +if (vma->vm_userfaultfd_ctx.ctx == ctx) +userfaultfd_reset_ctx (vma); + } +mmap_write_unlock (mm); +} + +void userfaultfd_release_all (struct mm_struct *mm, +struct userfaultfd_ctx *ctx) +{ +struct vm_area_struct *vma, *prev; +VMA_ITERATOR (vmi, mm,0 ); + +if (!mmget_not_zero (mm)) +return ; + +/* +* Flush page faults out of all CPUs. NOTE: all page faults +* must be retried without returning VM_FAULT_SIGBUS if +* userfaultfd_ctx_get() succeeds but vma->vma_userfault_ctx +* changes while handle_userfault released the mmap_lock. So +* it's critical that released is set to true (above), before +* taking the mmap_lock for writing. +*/ +mmap_write_lock (mm); + prev =NULL ; +for_each_vma (vmi, vma) { +cond_resched (); +BUG_ON (!!vma->vm_userfaultfd_ctx.ctx ^ + !!(vma->vm_flags & __VM_UFFD_FLAGS)); +if (vma->vm_userfaultfd_ctx.ctx != ctx) { + prev = vma; +continue ; + } + + vma =userfaultfd_clear_vma (&vmi, prev, vma, + vma->vm_start, vma->vm_end); + prev = vma; + } +mmap_write_unlock (mm); +mmput (mm); +}Signature · 1 line
2.45.2
Re: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
Quoted 9 lines · Pengfei Xu
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.Bisected the first bad commit:
4651ba8201cfuserfaultfd: move core VMA manipulation logic tomm/userfaultfd.c
Hi,
Thanks for this, I will investigate as a priority and work up a fix. As it's simply a refactor I suspect this should be relatively straightforward.
Quoted 651 lines
All detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ctx
Syzkaller repro code: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.c
Syzkaller repro syscall steps: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.prog
Syzkaller analysis report: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/repro.report
Kconfig(make olddefconfig): https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/kconfig_origin
Bisect info: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/bisect_info.log
Dmesg: https://github.com/xupengfe/syzkaller_logs/blob/main/240806_122723_userfaultfd_set_ctx/d6dbc9f56c3a70e915625b6f1887882c23dc5c91_dmesg.log
bzImage: https://github.com/xupengfe/syzkaller_logs/raw/main/240806_122723_userfaultfd_set_ctx/bzImage_d6dbc9f56c3a70e915625b6f1887882c23dc5c91.tar.gz"
[ 29.675551] ================================================================== [ 29.676133] BUG: KASAN: slab-use-after-free in userfaultfd_set_ctx+0x31c/0x360 [ 29.676716] Read of size 8 at addr ffff888027c5f100 by task repro/1498 [ 29.677218] [ 29.677358] CPU: 0 UID: 0 PID: 1498 Comm: repro Not tainted 6.11.0-rc2-next-20240805-d6dbc9f56c3a #1 [ 29.678053] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 [ 29.678910] Call Trace: [ 29.679117] <TASK> [ 29.679296] dump_stack_lvl+0xea/0x150 [ 29.679622] print_report+0xce/0x610 [ 29.679924] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.680289] ? kasan_complete_mode_report_info+0x80/0x200 [ 29.680716] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.681077] kasan_report+0xcc/0x110 [ 29.681372] ? userfaultfd_set_ctx+0x31c/0x360 [ 29.681729] __asan_report_load8_noabort+0x18/0x20 [ 29.682118] userfaultfd_set_ctx+0x31c/0x360 [ 29.682465] userfaultfd_clear_vma+0x104/0x190 [ 29.682826] userfaultfd_release_all+0x294/0x4a0 [ 29.683201] ? __pfx_userfaultfd_release_all+0x10/0x10 [ 29.683615] ? __this_cpu_preempt_check+0x21/0x30 [ 29.684003] ? __pfx_userfaultfd_release+0x10/0x10 [ 29.684389] userfaultfd_release+0x112/0x1e0 [ 29.684735] ? __pfx_userfaultfd_release+0x10/0x10 [ 29.685114] ? evm_file_release+0x193/0x1f0 [ 29.685454] __fput+0x426/0xbc0 [ 29.685719] ? __sanitizer_cov_trace_const_cmp2+0x1c/0x30 [ 29.686153] __fput_sync+0x58/0x70 [ 29.686435] __x64_sys_close+0x93/0x120 [ 29.686744] x64_sys_call+0x189a/0x20d0 [ 29.687066] do_syscall_64+0x6d/0x140 [ 29.687371] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.687779] RIP: 0033:0x7f3b67b3f247 [ 29.688078] Code: ff e8 cd e3 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 c3 c9 f5 ff [ 29.689519] RSP: 002b:00007ffd1f0ac7d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003 [ 29.690140] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3b67b3f247 [ 29.690717] RDX: 0000000020000100 RSI: 000000008010aa01 RDI: 0000000000000003 [ 29.691270] RBP: 00007ffd1f0ac7f0 R08: 00007ffd1f0ac7f0 R09: 00007ffd1f0ac7f0 [ 29.691822] R10: 00007ffd1f0ac7f0 R11: 0000000000000246 R12: 00007ffd1f0ac968 [ 29.692375] R13: 0000000000401bf9 R14: 0000000000403e08 R15: 00007f3b67c72000 [ 29.692939] </TASK> [ 29.693124] [ 29.693258] Allocated by task 1498: [ 29.693545] kasan_save_stack+0x2c/0x60 [ 29.693875] kasan_save_track+0x18/0x40 [ 29.694205] kasan_save_alloc_info+0x3c/0x50 [ 29.694576] __kasan_slab_alloc+0x62/0x80 [ 29.694921] kmem_cache_alloc_noprof+0x114/0x370 [ 29.695319] vm_area_dup+0x2a/0x1b0 [ 29.695630] __split_vma+0x188/0x1020 [ 29.695952] vma_modify+0x1fc/0x390 [ 29.696250] userfaultfd_clear_vma+0xd4/0x190 [ 29.696609] userfaultfd_ioctl+0x3c0b/0x4560 [ 29.696964] __x64_sys_ioctl+0x1b9/0x230 [ 29.697295] x64_sys_call+0x1209/0x20d0 [ 29.697620] do_syscall_64+0x6d/0x140 [ 29.697937] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.698364] [ 29.698508] Freed by task 1505: [ 29.698779] kasan_save_stack+0x2c/0x60 [ 29.699110] kasan_save_track+0x18/0x40 [ 29.699441] kasan_save_free_info+0x3f/0x60 [ 29.699797] __kasan_slab_free+0x47/0x60 [ 29.700137] kmem_cache_free+0x2f2/0x4b0 [ 29.700471] vm_area_free_rcu_cb+0x7f/0xa0 [ 29.700819] rcu_core+0x877/0x18f0 [ 29.701123] rcu_core_si+0x12/0x20 [ 29.701421] handle_softirqs+0x1c7/0x870 [ 29.701760] __irq_exit_rcu+0xa9/0x120 [ 29.702082] irq_exit_rcu+0x12/0x30 [ 29.702386] sysvec_apic_timer_interrupt+0xa5/0xc0 [ 29.702802] asm_sysvec_apic_timer_interrupt+0x1f/0x30 [ 29.703237] [ 29.703377] Last potentially related work creation: [ 29.703782] kasan_save_stack+0x2c/0x60 [ 29.704114] __kasan_record_aux_stack+0x93/0xb0 [ 29.704503] kasan_record_aux_stack_noalloc+0xf/0x20 [ 29.704923] __call_rcu_common.constprop.0+0x72/0x6b0 [ 29.705349] call_rcu+0x12/0x20 [ 29.705625] vm_area_free+0x26/0x30 [ 29.705928] vma_complete+0x57e/0xf60 [ 29.706245] vma_merge+0x166b/0x3540 [ 29.706555] vma_modify+0x9f/0x390 [ 29.706853] userfaultfd_clear_vma+0xd4/0x190 [ 29.707227] userfaultfd_release_all+0x294/0x4a0 [ 29.707621] userfaultfd_release+0x112/0x1e0 [ 29.707991] __fput+0x426/0xbc0 [ 29.708267] __fput_sync+0x58/0x70 [ 29.708563] __x64_sys_close+0x93/0x120 [ 29.708891] x64_sys_call+0x189a/0x20d0 [ 29.709220] do_syscall_64+0x6d/0x140 [ 29.709538] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 29.709965] [ 29.710105] The buggy address belongs to the object at ffff888027c5f0f0 [ 29.710105] which belongs to the cache vm_area_struct of size 176 [ 29.711130] The buggy address is located 16 bytes inside of [ 29.711130] freed 176-byte region [ffff888027c5f0f0, ffff888027c5f1a0) [ 29.712104] [ 29.712245] The buggy address belongs to the physical page: [ 29.712703] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x27c5f [ 29.713349] memcg:ffff8880198eaa01 [ 29.713639] flags: 0xfffffc0000000(node=0|zone=1|lastcpupid=0x1fffff) [ 29.714173] page_type: 0xfdffffff(slab) [ 29.714507] raw: 000fffffc0000000 ffff88800d319dc0 dead000000000122 0000000000000000 [ 29.715137] raw: 0000000000000000 0000000000110011 00000001fdffffff ffff8880198eaa01 [ 29.715765] page dumped because: kasan: bad access detected [ 29.716220] [ 29.716360] Memory state around the buggy address: [ 29.716756] ffff888027c5f000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 29.717349] ffff888027c5f080: 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fa fb [ 29.717940] >ffff888027c5f100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb [ 29.718521] ^ [ 29.718796] ffff888027c5f180: fb fb fb fb fc fc fc fc fc fc fc fc 00 00 00 00 [ 29.719388] ffff888027c5f200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 29.720025] ================================================================== [ 29.720671] Disabling lock debugging due to kernel taint"
Thanks!
---
If you don't need the following environment to reproduce the problem or if you already have one reproduced environment, please ignore the following information.
How to reproduce:
git clone https://gitlab.com/xupengfe/repro_vm_env.git
cdrepro_vm_env
tar -xvf repro_vm_env.tar.gz
cdrepro_vm_env; ./start3.sh // it needs qemu-system-x86_64 and I used v7.1.0
//start3.shwill loadbzImage_2241ab53cbb5cdb08a6b2d4688feb13971058f65v6.2-rc5 kernel
// You could change thebzImage_xxxas you want
// Maybe you need to remove line "-drive if=pflash,format=raw,readonly=on,file=./OVMF_CODE.fd \" for different qemu version
You could use below command to log in, there is no password for root.
ssh -p 10023 root@localhostAfter login vm(virtual machine) successfully, you could transfer reproduced binary to the vm by below way, and reproduce the problem in vm:
gcc -pthread -o reprorepro.c
scp -P 10023 repro root@localhost:/root/Get the bzImage for target kernel:
Please use target kconfig and copy it to kernel_src/.config make olddefconfig
make -jx bzImage //x should equal or less than cpu num your pc hasFill the bzImage file into above
start3.shto load the target kernel in vm.Tips:
If you already have qemu-system-x86_64, please ignore below info.
If you want to install qemu v7.1.0 version:
git clone https://github.com/qemu/qemu.git
cd qemu
git checkout -f v7.1.0
mkdir build
cd build
yum install -y ninja-build.x86_64
yum -y install libslirp-devel.x86_64
../configure --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-sdl --enable-usb-redir --enable-slirp make
make installBest Regards,
Thanks!Quoted 472 lines · Lorenzo Stoakes
This patch forms part of a patch series intending to separate out VMA logic and render it testable from userspace, which requires that core manipulation functions be exposed in an
mm/-internalheader file.In order to do this, we must abstract APIs we wish to test, in this instance functions which ultimately invoke
vma_modify().This patch therefore moves all logic which ultimately invokes
vma_modify()tomm/userfaultfd.c, trying to transfer code at a functional granularity where possible.Reviewed-by Vlastimil Babka <[email protected]>Reviewed-by Liam R. Howlett <[email protected]>Signed-off-by Lorenzo Stoakes <[email protected]>--- fs/userfaultfd.c | 160 +++----------------------------- include/linux/userfaultfd_k.h | 19 ++++ mm/userfaultfd.c | 168 ++++++++++++++++++++++++++++++++++ 3 files changed, 198 insertions(+), 149 deletions(-)fs/userfaultfd.c +11
-149@@ -104,21 +104,6 @@ bool userfaultfd_wp_unpopulated(struct vm_area_struct *vma)return ctx->features &UFFD_FEATURE_WP_UNPOPULATED ; } -static void userfaultfd_set_vm_flags (struct vm_area_struct *vma, -vm_flags_t flags) -{ -const bool uffd_wp_changed = (vma->vm_flags ^ flags) &VM_UFFD_WP ; - -vm_flags_reset (vma, flags); -/* -* For shared mappings, we want to enable writenotify while -* userfaultfd-wp is enabled (see vma_wants_writenotify()). We'll simply -* recalculate vma->vm_page_prot whenever userfaultfd-wp changes. -*/ -if ((vma->vm_flags &VM_SHARED ) && uffd_wp_changed) -vma_set_page_prot (vma); -} -static int userfaultfd_wake_function (wait_queue_entry_t *wq,unsigned mode,int wake_flags,void *key) {@@ -615,22 +600,7 @@ static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,spin_unlock_irq (&ctx->event_wqh.lock);if (release_new_ctx) { -struct vm_area_struct *vma; -struct mm_struct *mm = release_new_ctx->mm; -VMA_ITERATOR (vmi, mm,0 ); - -/* the various vma->vm_userfaultfd_ctx still points to it */ -mmap_write_lock (mm); -for_each_vma (vmi, vma) { -if (vma->vm_userfaultfd_ctx.ctx == release_new_ctx) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, - vma->vm_flags & ~__VM_UFFD_FLAGS); - } - } -mmap_write_unlock (mm); - +userfaultfd_release_new (release_new_ctx);userfaultfd_ctx_put (release_new_ctx); }@@ -662,9 +632,7 @@ int dup_userfaultfd(struct vm_area_struct *vma, struct list_head *fcs)return 0 ;if (!(octx->features &UFFD_FEATURE_EVENT_FORK )) { -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma);return 0 ; }@@ -749,9 +717,7 @@ void mremap_userfaultfd_prep(struct vm_area_struct *vma,up_write (&ctx->map_changing_lock); }else {/* Drop uffd context if remap feature not enabled */ -vma_start_write (vma); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; -userfaultfd_set_vm_flags (vma, vma->vm_flags & ~__VM_UFFD_FLAGS); +userfaultfd_reset_ctx (vma); } }@@ -870,53 +836,13 @@ static int userfaultfd_release(struct inode *inode, struct file *file) {struct userfaultfd_ctx *ctx = file->private_data;struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev;/* len == 0 means wake all */ struct userfaultfd_wake_range range = { .len =0 , }; -unsigned long new_flags; -VMA_ITERATOR (vmi, mm,0 );WRITE_ONCE (ctx->released, true); -if (!mmget_not_zero (mm)) - goto wakeup; - -/* -* Flush page faults out of all CPUs. NOTE: all page faults -* must be retried without returning VM_FAULT_SIGBUS if -* userfaultfd_ctx_get() succeeds but vma->vma_userfault_ctx -* changes while handle_userfault released the mmap_lock. So -* it's critical that released is set to true (above), before -* taking the mmap_lock for writing. -*/ -mmap_write_lock (mm); - prev =NULL ; -for_each_vma (vmi, vma) { -cond_resched (); -BUG_ON (!!vma->vm_userfaultfd_ctx.ctx ^ - !!(vma->vm_flags & __VM_UFFD_FLAGS)); -if (vma->vm_userfaultfd_ctx.ctx != ctx) { - prev = vma; -continue ; - } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, vma->vm_start, - vma->vm_end - vma->vm_start, false); - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, vma->vm_start, - vma->vm_end, new_flags, -NULL_VM_UFFD_CTX ); - -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; +userfaultfd_release_all (mm, ctx); - prev = vma; - } -mmap_write_unlock (mm); -mmput (mm); -wakeup:/* * After no new page faults can wait on this fault_*wqh, flush * the last page faults that may have been already waiting on @@ -1293,14 +1219,14 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, unsigned long arg) {struct mm_struct *mm = ctx->mm; -struct vm_area_struct *vma, *prev, *cur; +struct vm_area_struct *vma, *cur;int ret;struct uffdio_register uffdio_register;struct uffdio_register __user *user_uffdio_register; -unsigned long vm_flags, new_flags; +unsigned long vm_flags;bool found;bool basic_ioctls; -unsigned long start, end, vma_end; +unsigned long start, end;struct vma_iterator vmi;bool wp_async =userfaultfd_wp_async_ctx (ctx);@@ -1428,57 +1354,8 @@ static int userfaultfd_register(struct userfaultfd_ctx *ctx, }for_each_vma_range (vmi, cur, end);BUG_ON (!found); -vma_iter_set (&vmi, start); - prev =vma_prev (&vmi); -if (vma->vm_start < start) - prev = vma; - - ret =0 ; -for_each_vma_range (vmi, vma, end) { -cond_resched (); - -BUG_ON (!vma_can_userfault (vma, vm_flags, wp_async)); -BUG_ON (vma->vm_userfaultfd_ctx.ctx && - vma->vm_userfaultfd_ctx.ctx != ctx); -WARN_ON (!(vma->vm_flags &VM_MAYWRITE )); - -/* -* Nothing to do: this vma is already registered into this -* userfaultfd and with the right tracking mode too. -*/ -if (vma->vm_userfaultfd_ctx.ctx == ctx && - (vma->vm_flags & vm_flags) == vm_flags) - goto skip; - -if (vma->vm_start > start) - start = vma->vm_start; - vma_end =min (end, vma->vm_end); - - new_flags = (vma->vm_flags & ~__VM_UFFD_FLAGS) | vm_flags; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags, - (struct vm_userfaultfd_ctx ){ctx}); -if (IS_ERR (vma)) { - ret =PTR_ERR (vma); -break ; - } - -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx.ctx = ctx; - -if (is_vm_hugetlb_page (vma) &&uffd_disable_huge_pmd_share (vma)) -hugetlb_unshare_all_pmds (vma); - - skip: - prev = vma; - start = vma->vm_end; - } + ret =userfaultfd_register_range (ctx, vma, vm_flags, start, end, + wp_async); out_unlock:mmap_write_unlock (mm);@@ -1519,7 +1396,6 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,struct vm_area_struct *vma, *prev, *cur;int ret;struct uffdio_range uffdio_unregister; -unsigned long new_flags;bool found;unsigned long start, end, vma_end;const void __user *buf = (void __user *)arg;@@ -1622,27 +1498,13 @@ static int userfaultfd_unregister(struct userfaultfd_ctx *ctx,wake_userfault (vma->vm_userfaultfd_ctx.ctx, &range); } -/* Reset ptes for the whole vma range if wr-protected */ -if (userfaultfd_wp (vma)) -uffd_wp_range (vma, start, vma_end - start, false); - - new_flags = vma->vm_flags & ~__VM_UFFD_FLAGS; - vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, - new_flags,NULL_VM_UFFD_CTX ); + vma =userfaultfd_clear_vma (&vmi, prev, vma, + start, vma_end);if (IS_ERR (vma)) { ret =PTR_ERR (vma);break ; } -/* -* In the vma_merge() successful mprotect-like case 8: -* the next vma was merged into the current one and -* the current one has not been updated yet. -*/ -vma_start_write (vma); -userfaultfd_set_vm_flags (vma, new_flags); - vma->vm_userfaultfd_ctx =NULL_VM_UFFD_CTX ; - skip: prev = vma; start = vma->vm_end;include/linux/userfaultfd_k.h +19
-0@@ -267,6 +267,25 @@ extern void userfaultfd_unmap_complete(struct mm_struct *mm,extern bool userfaultfd_wp_unpopulated (struct vm_area_struct *vma);extern bool userfaultfd_wp_async (struct vm_area_struct *vma); +void userfaultfd_reset_ctx (struct vm_area_struct *vma); + +struct vm_area_struct *userfaultfd_clear_vma (struct vma_iterator *vmi, +struct vm_area_struct *prev, +struct vm_area_struct *vma, +unsigned long start, +unsigned long end); + +int userfaultfd_register_range (struct userfaultfd_ctx *ctx, +struct vm_area_struct *vma, +unsigned long vm_flags, +unsigned long start,unsigned long end, +bool wp_async); + +void userfaultfd_release_new (struct userfaultfd_ctx *ctx); + +void userfaultfd_release_all (struct mm_struct *mm, +struct userfaultfd_ctx *ctx); +#else /* CONFIG_USERFAULTFD */ /* mm helpers */ mm/userfaultfd.c +168
-1@@ -1760,3 +1760,171 @@ ssize_t move_pages(struct userfaultfd_ctx *ctx, unsigned long dst_start,VM_WARN_ON (!moved && !err);return moved ? moved : err; } + +static void userfaultfd_set_vm_flags (struct vm_area_struct *vma, +vm_flags_t flags) +{ +const bool uffd_wp_changed = (vma->vm_flags ^ flags) &VM_UFFD_WP ; + +vm_flags_reset (vma, flags); +/* +* For shared mappings, we want to enable writenotify while +* userfaultfd-wp is enabled (see vma_wants_writenotify()). We'll simply +* recalculate vma->vm_page_prot whenever userfaultfd-wp changes. +*/ +if ((vma->vm_flags &VM_SHARED ) && uffd_wp_changed) +vma_set_page_prot (vma); +} + +static void userfaultfd_set_ctx (struct vm_area_struct *vma, +struct userfaultfd_ctx *ctx, +unsigned long flags) +{ +vma_start_write (vma); + vma->vm_userfaultfd_ctx = (struct vm_userfaultfd_ctx ){ctx}; +userfaultfd_set_vm_flags (vma, + (vma->vm_flags & ~__VM_UFFD_FLAGS) | flags); +} + +void userfaultfd_reset_ctx (struct vm_area_struct *vma) +{ +userfaultfd_set_ctx (vma,NULL ,0 ); +} + +struct vm_area_struct *userfaultfd_clear_vma (struct vma_iterator *vmi, +struct vm_area_struct *prev, +struct vm_area_struct *vma, +unsigned long start, +unsigned long end) +{ +struct vm_area_struct *ret; + +/* Reset ptes for the whole vma range if wr-protected */ +if (userfaultfd_wp (vma)) +uffd_wp_range (vma, start, end - start, false); + + ret =vma_modify_flags_uffd (vmi, prev, vma, start, end, + vma->vm_flags & ~__VM_UFFD_FLAGS, +NULL_VM_UFFD_CTX ); + +/* +* In the vma_merge() successful mprotect-like case 8: +* the next vma was merged into the current one and +* the current one has not been updated yet. +*/ +if (!IS_ERR (ret)) +userfaultfd_reset_ctx (vma); + +return ret; +} + +/* Assumes mmap write lock taken, and mm_struct pinned. */ +int userfaultfd_register_range (struct userfaultfd_ctx *ctx, +struct vm_area_struct *vma, +unsigned long vm_flags, +unsigned long start,unsigned long end, +bool wp_async) +{ +VMA_ITERATOR (vmi, ctx->mm, start); +struct vm_area_struct *prev =vma_prev (&vmi); +unsigned long vma_end; +unsigned long new_flags; + +if (vma->vm_start < start) + prev = vma; + +for_each_vma_range (vmi, vma, end) { +cond_resched (); + +BUG_ON (!vma_can_userfault (vma, vm_flags, wp_async)); +BUG_ON (vma->vm_userfaultfd_ctx.ctx && + vma->vm_userfaultfd_ctx.ctx != ctx); +WARN_ON (!(vma->vm_flags &VM_MAYWRITE )); + +/* +* Nothing to do: this vma is already registered into this +* userfaultfd and with the right tracking mode too. +*/ +if (vma->vm_userfaultfd_ctx.ctx == ctx && + (vma->vm_flags & vm_flags) == vm_flags) + goto skip; + +if (vma->vm_start > start) + start = vma->vm_start; + vma_end =min (end, vma->vm_end); + + new_flags = (vma->vm_flags & ~__VM_UFFD_FLAGS) | vm_flags; + vma =vma_modify_flags_uffd (&vmi, prev, vma, start, vma_end, + new_flags, + (struct vm_userfaultfd_ctx ){ctx}); +if (IS_ERR (vma)) +return PTR_ERR (vma); + +/* +* In the vma_merge() successful mprotect-like case 8: +* the next vma was merged into the current one and +* the current one has not been updated yet. +*/ +userfaultfd_set_ctx (vma, ctx, vm_flags); + +if (is_vm_hugetlb_page (vma) &&uffd_disable_huge_pmd_share (vma)) +hugetlb_unshare_all_pmds (vma); + +skip: + prev = vma; + start = vma->vm_end; + } + +return 0 ; +} + +void userfaultfd_release_new (struct userfaultfd_ctx *ctx) +{ +struct mm_struct *mm = ctx->mm; +struct vm_area_struct *vma; +VMA_ITERATOR (vmi, mm,0 ); + +/* the various vma->vm_userfaultfd_ctx still points to it */ +mmap_write_lock (mm); +for_each_vma (vmi, vma) { +if (vma->vm_userfaultfd_ctx.ctx == ctx) +userfaultfd_reset_ctx (vma); + } +mmap_write_unlock (mm); +} + +void userfaultfd_release_all (struct mm_struct *mm, +struct userfaultfd_ctx *ctx) +{ +struct vm_area_struct *vma, *prev; +VMA_ITERATOR (vmi, mm,0 ); + +if (!mmget_not_zero (mm)) +return ; + +/* +* Flush page faults out of all CPUs. NOTE: all page faults +* must be retried without returning VM_FAULT_SIGBUS if +* userfaultfd_ctx_get() succeeds but vma->vma_userfault_ctx +* changes while handle_userfault released the mmap_lock. So +* it's critical that released is set to true (above), before +* taking the mmap_lock for writing. +*/ +mmap_write_lock (mm); + prev =NULL ; +for_each_vma (vmi, vma) { +cond_resched (); +BUG_ON (!!vma->vm_userfaultfd_ctx.ctx ^ + !!(vma->vm_flags & __VM_UFFD_FLAGS)); +if (vma->vm_userfaultfd_ctx.ctx != ctx) { + prev = vma; +continue ; + } + + vma =userfaultfd_clear_vma (&vmi, prev, vma, + vma->vm_start, vma->vm_end); + prev = vma; + } +mmap_write_unlock (mm); +mmput (mm); +} --2.45.2
Re: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
In reply to Pengfei XuQuoted 11 lines · Pengfei Xu
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.Bisected the first bad commit:
4651ba8201cfuserfaultfd: move core VMA manipulation logic tomm/userfaultfd.cAll detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ct
[snip]
Andrew - As this is so small, could you take this as a fix-patch? The fix is enclosed below.
Pengfei - Sorry for the delay on getting this resolved, I was struggling to repro with my usual dev setup, after trying a lot of things I ended up using the supplied repro env and was able to do so there.
(I suspect that VMAs are laid out slightly differently in my usual arch base image perhaps based on tunables, and this was the delta on that!)
Regardless, I was able to identify the cause - we incorrectly pass a stale pointer to userfaultfd_reset_ctx() if a merge is performed in userfaultfd_clear_vma().
This was a subtle mistake on my part, I don't see any other instances like this in the patch.
Syzkaller managed to get this merge to happen and kasan picked up on it, so thank you very much for supplying the infra!
The fix itself is very simple, a one-liner, enclosed below.
----8<----
From 193abd1c3a51e6bf1d85ddfe01845e9713336970 Mon Sep 17 00:00:00 2001
From: Lorenzo Stoakes <[email protected]>
Date: Wed, 7 Aug 2024 12:44:27 +0100
Subject: [PATCH] mm: userfaultfd: fix user-after-free in
userfaultfd_clear_vma()
After invoking vma_modify_flags_uffd() in userfaultfd_clear_vma(), we may have merged the vma, and depending on the kind of merge, deleted the vma, rendering the vma pointer invalid.
The code incorrectly referenced this now possibly invalid vma pointer when invoking userfaultfd_reset_ctx().
If no merge is possible, vma_modify_flags_uffd() performs a split and returns the original vma. Therefore the correct approach is to simply pass the ret pointer to userfaultfd_ret_ctx().
--- mm/userfaultfd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/userfaultfd.c +1 -1
@@ -1813,7 +1813,7 @@ struct vm_area_struct *userfaultfd_clear_vma(struct vma_iterator *vmi,* the current one has not been updated yet. */ if (!IS_ERR (ret)) -userfaultfd_reset_ctx (vma); +userfaultfd_reset_ctx (ret);return ret; }
--
2.45.2
Re: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
Hi Lorenzo Stoakes,
Quoted 30 lines · Lorenzo Stoakes
Quoted 11 lines · Pengfei Xu
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.Bisected the first bad commit:
4651ba8201cfuserfaultfd: move core VMA manipulation logic tomm/userfaultfd.cAll detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ct
[snip]
Andrew - As this is so small, could you take this as a fix-patch? The fix is enclosed below.
Pengfei - Sorry for the delay on getting this resolved, I was struggling to repro with my usual dev setup, after trying a lot of things I ended up using the supplied repro env and was able to do so there.
(I suspect that VMAs are laid out slightly differently in my usual arch base image perhaps based on tunables, and this was the delta on that!)
Regardless, I was able to identify the cause - we incorrectly pass a stale pointer to
userfaultfd_reset_ctx()if a merge is performed inuserfaultfd_clear_vma().
Quoted 8 lines
This was a subtle mistake on my part, I don't see any other instances like this in the patch.
Syzkaller managed to get this merge to happen and kasan picked up on it, so thank you very much for supplying the infra!
The fix itself is very simple, a one-liner, enclosed below.
Thanks for your patch!
I tested the below patch on top of next-20240805, this issue could not be reproduced. So it's fixed.
Best Regrads,
Thanks!
Quoted 41 lines
----8<----
From193abd1c3a51e6bf1d85ddfe01845e9713336970Mon Sep 17 00:00:00 2001
From: Lorenzo Stoakes <[email protected]>
Date: Wed, 7 Aug 2024 12:44:27 +0100
Subject: [PATCH] mm: userfaultfd: fix user-after-free in
userfaultfd_clear_vma()After invoking
vma_modify_flags_uffd()inuserfaultfd_clear_vma(), we may have merged the vma, and depending on the kind of merge, deleted the vma, rendering the vma pointer invalid.The code incorrectly referenced this now possibly invalid vma pointer when invoking
userfaultfd_reset_ctx().If no merge is possible,
vma_modify_flags_uffd()performs a split and returns the original vma. Therefore the correct approach is to simply pass the ret pointer touserfaultfd_ret_ctx().Reported-by Pengfei Xu <[email protected]>Fixes e310f2b78a77 ("userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c")Signed-off-by Lorenzo Stoakes <[email protected]>--- mm/userfaultfd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)mm/userfaultfd.c +1
-2@@ -1813,7 +1813,7 @@ struct vm_area_struct *userfaultfd_clear_vma(struct vma_iterator *vmi,* the current one has not been updated yet. */ if (!IS_ERR (ret)) -userfaultfd_reset_ctx (vma); +userfaultfd_reset_ctx (ret);return ret; } --2.45.2
Vlastimil Babka
Acked-byRe: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
In reply to Lorenzo StoakesQuoted 52 lines · Lorenzo Stoakes
Quoted 11 lines · Pengfei Xu
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.Bisected the first bad commit:
4651ba8201cfuserfaultfd: move core VMA manipulation logic tomm/userfaultfd.cAll detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ct
[snip]
Andrew - As this is so small, could you take this as a fix-patch? The fix is enclosed below.
Pengfei - Sorry for the delay on getting this resolved, I was struggling to repro with my usual dev setup, after trying a lot of things I ended up using the supplied repro env and was able to do so there.
(I suspect that VMAs are laid out slightly differently in my usual arch base image perhaps based on tunables, and this was the delta on that!)
Regardless, I was able to identify the cause - we incorrectly pass a stale pointer to
userfaultfd_reset_ctx()if a merge is performed inuserfaultfd_clear_vma().This was a subtle mistake on my part, I don't see any other instances like this in the patch.
Syzkaller managed to get this merge to happen and kasan picked up on it, so thank you very much for supplying the infra!
The fix itself is very simple, a one-liner, enclosed below.
----8<----
From193abd1c3a51e6bf1d85ddfe01845e9713336970Mon Sep 17 00:00:00 2001
From: Lorenzo Stoakes <[email protected]>
Date: Wed, 7 Aug 2024 12:44:27 +0100
Subject: [PATCH] mm: userfaultfd: fix user-after-free in
userfaultfd_clear_vma()After invoking
vma_modify_flags_uffd()inuserfaultfd_clear_vma(), we may have merged the vma, and depending on the kind of merge, deleted the vma, rendering the vma pointer invalid.The code incorrectly referenced this now possibly invalid vma pointer when invoking
userfaultfd_reset_ctx().
Quoted 8 lines
If no merge is possible,
vma_modify_flags_uffd()performs a split and returns the original vma. Therefore the correct approach is to simply pass the ret pointer touserfaultfd_ret_ctx().Reported-by Pengfei Xu <[email protected]>Fixes e310f2b78a77 ("userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c")Signed-off-by Lorenzo Stoakes <[email protected]>
Quoted 19 lines
--- mm/userfaultfd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)mm/userfaultfd.c +1
-2@@ -1813,7 +1813,7 @@ struct vm_area_struct *userfaultfd_clear_vma(struct vma_iterator *vmi,* the current one has not been updated yet. */ if (!IS_ERR (ret)) -userfaultfd_reset_ctx (vma); +userfaultfd_reset_ctx (ret);return ret; } --2.45.2
Re: [PATCH v4 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c
In reply to Lorenzo StoakesHi Lorenzo Stoakes,
Quoted 15 lines · Lorenzo Stoakes
Quoted 11 lines · Pengfei Xu
Hi Lorenzo Stoakes,
Greetings!
I used syzkaller and found
KASAN: slab-use-after-free Read in userfaultfd_set_ctx in next-20240805.Bisected the first bad commit:
4651ba8201cfuserfaultfd: move core VMA manipulation logic tomm/userfaultfd.cAll detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/240806_122723_userfaultfd_set_ct
[snip]
Quoted 7 lines
Andrew - As this is so small, could you take this as a fix-patch? The fix is enclosed below.
Pengfei - Sorry for the delay on getting this resolved, I was struggling to repro with my usual dev setup, after trying a lot of things I ended up using the supplied repro env and was able to do so there.
Glad to know the repro environment is helpful.
Thank you for your patch(I verified it's fixed) and it helps me learn more.
Quoted 8 lines
(I suspect that VMAs are laid out slightly differently in my usual arch base image perhaps based on tunables, and this was the delta on that!)
Regardless, I was able to identify the cause - we incorrectly pass a stale pointer to
userfaultfd_reset_ctx()if a merge is performed inuserfaultfd_clear_vma().
Quoted 5 lines
This was a subtle mistake on my part, I don't see any other instances like this in the patch.
Syzkaller managed to get this merge to happen and kasan picked up on it, so thank you very much for supplying the infra!
You are welcome. :)
Best Regards,
Thank you!
Quoted 44 lines
The fix itself is very simple, a one-liner, enclosed below.
----8<----
From193abd1c3a51e6bf1d85ddfe01845e9713336970Mon Sep 17 00:00:00 2001
From: Lorenzo Stoakes <[email protected]>
Date: Wed, 7 Aug 2024 12:44:27 +0100
Subject: [PATCH] mm: userfaultfd: fix user-after-free in
userfaultfd_clear_vma()After invoking
vma_modify_flags_uffd()inuserfaultfd_clear_vma(), we may have merged the vma, and depending on the kind of merge, deleted the vma, rendering the vma pointer invalid.The code incorrectly referenced this now possibly invalid vma pointer when invoking
userfaultfd_reset_ctx().If no merge is possible,
vma_modify_flags_uffd()performs a split and returns the original vma. Therefore the correct approach is to simply pass the ret pointer touserfaultfd_ret_ctx().Reported-by Pengfei Xu <[email protected]>Fixes e310f2b78a77 ("userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c")Signed-off-by Lorenzo Stoakes <[email protected]>--- mm/userfaultfd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)mm/userfaultfd.c +1
-2@@ -1813,7 +1813,7 @@ struct vm_area_struct *userfaultfd_clear_vma(struct vma_iterator *vmi,* the current one has not been updated yet. */ if (!IS_ERR (ret)) -userfaultfd_reset_ctx (vma); +userfaultfd_reset_ctx (ret);return ret; } --2.45.2
PATCH v4 2/7 mm: move vma_modify() and helpers to internal header
In reply to Lorenzo StoakesThese are core VMA manipulation functions which invoke VMA splitting and merging and should not be directly accessed from outside of mm/.
--- include/linux/mm.h | 60 --------------------------------------------- mm/internal.h | 61 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 61 insertions(+), 60 deletions(-)
include/linux/mm.h +0 -60
@@ -3278,66 +3278,6 @@ extern struct vm_area_struct *copy_vma(struct vm_area_struct **, unsigned long addr, unsigned long len, pgoff_t pgoff, bool *need_rmap_locks);extern void exit_mmap (struct mm_struct *); -struct vm_area_struct *vma_modify (struct vma_iterator *vmi, -struct vm_area_struct *prev, -struct vm_area_struct *vma, -unsigned long start,unsigned long end, -unsigned long vm_flags, -struct mempolicy *policy, -struct vm_userfaultfd_ctx uffd_ctx, -struct anon_vma_name *anon_name); - -/* We are about to modify the VMA's flags. */ -static inline struct vm_area_struct -*vma_modify_flags (struct vma_iterator *vmi, -struct vm_area_struct *prev, -struct vm_area_struct *vma, -unsigned long start,unsigned long end, -unsigned long new_flags) -{ -return vma_modify (vmi, prev, vma, start, end, new_flags, -vma_policy (vma), vma->vm_userfaultfd_ctx, -anon_vma_name (vma)); -} - -/* We are about to modify the VMA's flags and/or anon_name. */ -static inline struct vm_area_struct -*vma_modify_flags_name (struct vma_iterator *vmi, -struct vm_area_struct *prev, -struct vm_area_struct *vma, -unsigned long start, -unsigned long end, -unsigned long new_flags, -struct anon_vma_name *new_name) -{ -return vma_modify (vmi, prev, vma, start, end, new_flags, -vma_policy (vma), vma->vm_userfaultfd_ctx, new_name); -} - -/* We are about to modify the VMA's memory policy. */ -static inline struct vm_area_struct -*vma_modify_policy (struct vma_iterator *vmi, -struct vm_area_struct *prev, -struct vm_area_struct *vma, -unsigned long start,unsigned long end, -struct mempolicy *new_pol) -{ -return vma_modify (vmi, prev, vma, start, end, vma->vm_flags, - new_pol, vma->vm_userfaultfd_ctx,anon_vma_name (vma)); -} - -/* We are about to modify the VMA's flags and/or uffd context. */ -static inline struct vm_area_struct -*vma_modify_flags_uffd (struct vma_iterator *vmi, -struct vm_area_struct *prev, -struct vm_area_struct *vma, -unsigned long start,unsigned long end, -unsigned long new_flags, -struct vm_userfaultfd_ctx new_ctx) -{ -return vma_modify (vmi, prev, vma, start, end, new_flags, -vma_policy (vma), new_ctx,anon_vma_name (vma)); -} static inline int check_data_rlimit(unsigned long rlim, unsigned long new,
mm/internal.h +61 -0
67 lines not on this page · raw message
Signature · 1 line
2.45.2
PATCH v4 3/7 mm: move vma_shrink(), vma_expand() to internal header
In reply to Lorenzo StoakesThe vma_shrink() and vma_expand() functions are internal VMA manipulation functions which we ought to abstract for use outside of memory management code.
To achieve this, we replace shift_arg_pages() in fs/exec.c with an invocation of a new relocate_vma_down() function implemented in mm/mmap.c, which enables us to also move move_page_tables() and vma_iter_prev_range() to internal.h.
The purpose of doing this is to isolate key VMA manipulation functions in order that we can both abstract them and later render them easily testable.
--- fs/exec.c | 81 ++++------------------------------------------ include/linux/mm.h | 17 +--------- mm/internal.h | 18 +++++++++++ mm/mmap.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 106 insertions(+), 91 deletions(-)
fs/exec.c +6 -75
@@ -711,80 +711,6 @@ static int copy_strings_kernel(int argc, const char *const *argv,#ifdef CONFIG_MMU -/* -* During bprm_mm_init(), we create a temporary stack at STACK_TOP_MAX. Once -* the binfmt code determines where the new stack should reside, we shift it to -* its final location. The process proceeds as follows: -* -* 1) Use shift to calculate the new vma endpoints. -* 2) Extend vma to cover both the old and new ranges. This ensures the -* arguments passed to subsequent functions are consistent. -* 3) Move vma's page tables to the new range. -* 4) Free up any cleared pgd range. -* 5) Shrink the vma to cover only the new range. -*/ -static int shift_arg_pages (struct vm_area_struct *vma,unsigned long shift) -{ -struct mm_struct *mm = vma->vm_mm; -unsigned long old_start = vma->vm_start; -unsigned long old_end = vma->vm_end; -unsigned long length = old_end - old_start; -unsigned long new_start = old_start - shift; -unsigned long new_end = old_end - shift; -VMA_ITERATOR (vmi, mm, new_start); -struct vm_area_struct *next; -struct mmu_gather tlb; - -BUG_ON (new_start > new_end); - -/* -* ensure there are no vmas between where we want to go -* and where we are -*/ -if (vma !=vma_next (&vmi)) -return -EFAULT ; - -vma_iter_prev_range (&vmi); -/* -* cover the whole range: [new_start, old_end) -*/ -if (vma_expand (&vmi, vma, new_start, old_end, vma->vm_pgoff,NULL )) -return -ENOMEM ; - -/* -* move the page tables downwards, on failure we rely on -* process cleanup to remove whatever mess we made. -*/ -if (length !=move_page_tables (vma, old_start, - vma, new_start, length, false, true)) -return -ENOMEM ; - -lru_add_drain (); -tlb_gather_mmu (&tlb, mm); - next =vma_next (&vmi); -if (new_end > old_start) { -/* -* when the old and new regions overlap clear from new_end. -*/ -free_pgd_range (&tlb, new_end, old_end, new_end, - next ? next->vm_start :USER_PGTABLES_CEILING ); - }else { -/* -* otherwise, clean from old_start; this is done to not touch -* the address space in [new_end, old_start) some architectures -* have constraints on va-space that make this illegal (IA64) - -* for the others its just a little faster. -*/ -free_pgd_range (&tlb, old_start, old_end, new_end, - next ? next->vm_start :USER_PGTABLES_CEILING ); - } -tlb_finish_mmu (&tlb); - -vma_prev (&vmi); -/* Shrink the vma to just the new range */ -return vma_shrink (&vmi, vma, new_start, new_end, vma->vm_pgoff); -} -/* * Finalizes the stack vm_area_struct. The flags and permissions are updated, * the stack is optionally relocated, and some extra space is added.
@@ -877,7 +803,12 @@ int setup_arg_pages(struct linux_binprm *bprm,/* Move stack pages down in memory. */ if (stack_shift) { - ret =shift_arg_pages (vma, stack_shift); +/* +* During bprm_mm_init(), we create a temporary stack at STACK_TOP_MAX. Once +* the binfmt code determines where the new stack should reside, we shift it to +* its final location. +*/ + ret =relocate_vma_down (vma, stack_shift);if (ret) goto out_unlock; }
include/linux/mm.h +1 -16
@@ -1005,12 +1005,6 @@ static inline struct vm_area_struct *vma_prev(struct vma_iterator *vmi)return mas_prev (&vmi->mas,0 ); } -static inline -struct vm_area_struct *vma_iter_prev_range (struct vma_iterator *vmi) -{ -return mas_prev_range (&vmi->mas,0 ); -} -static inline unsigned long vma_iter_addr (struct vma_iterator *vmi) {return vmi->mas.index;
@@ -2530,11 +2524,6 @@ int set_page_dirty_lock(struct page *page);int get_cmdline (struct task_struct *task,char *buffer,int buflen); -extern unsigned long move_page_tables (struct vm_area_struct *vma, -unsigned long old_addr,struct vm_area_struct *new_vma, -unsigned long new_addr,unsigned long len, -bool need_rmap_locks,bool for_stack); -/* * Flags used by change_protection(). For now we make it a bitmap so * that we can pass in multiple flags just like parameters. However
@@ -3266,11 +3255,6 @@ void anon_vma_interval_tree_verify(struct anon_vma_chain *node);/* mmap.c */ extern int __vm_enough_memory (struct mm_struct *mm,long pages,int cap_sys_admin); -extern int vma_expand (struct vma_iterator *vmi,struct vm_area_struct *vma, -unsigned long start,unsigned long end,pgoff_t pgoff, -struct vm_area_struct *next); -extern int vma_shrink (struct vma_iterator *vmi,struct vm_area_struct *vma, -unsigned long start,unsigned long end,pgoff_t pgoff);extern struct anon_vma *find_mergeable_anon_vma (struct vm_area_struct *);extern int insert_vm_struct (struct mm_struct *,struct vm_area_struct *);extern void unlink_file_vma (struct vm_area_struct *);
@@ -3278,6 +3262,7 @@ extern struct vm_area_struct *copy_vma(struct vm_area_struct **, unsigned long addr, unsigned long len, pgoff_t pgoff, bool *need_rmap_locks);extern void exit_mmap (struct mm_struct *); +int relocate_vma_down (struct vm_area_struct *vma,unsigned long shift); static inline int check_data_rlimit(unsigned long rlim, unsigned long new,
mm/internal.h +18 -0
@@ -1305,6 +1305,12 @@ static inline struct vm_area_struct vma_policy(vma), new_ctx, anon_vma_name(vma)); } +int vma_expand (struct vma_iterator *vmi,struct vm_area_struct *vma, +unsigned long start,unsigned long end,pgoff_t pgoff, +struct vm_area_struct *next); +int vma_shrink (struct vma_iterator *vmi,struct vm_area_struct *vma, +unsigned long start,unsigned long end,pgoff_t pgoff); +enum {/* mark page accessed */ FOLL_TOUCH =1 <<16 ,
@@ -1528,6 +1534,12 @@ static inline int vma_iter_store_gfp(struct vma_iterator *vmi,return 0 ; } +static inline +struct vm_area_struct *vma_iter_prev_range (struct vma_iterator *vmi) +{ +return mas_prev_range (&vmi->mas,0 ); +} +/* * VMA lock generalization */
@@ -1639,4 +1651,10 @@ void unlink_file_vma_batch_init(struct unlink_vma_file_batch *);void unlink_file_vma_batch_add (struct unlink_vma_file_batch *,struct vm_area_struct *);void unlink_file_vma_batch_final (struct unlink_vma_file_batch *); +/* mremap.c */ +unsigned long move_page_tables (struct vm_area_struct *vma, +unsigned long old_addr,struct vm_area_struct *new_vma, +unsigned long new_addr,unsigned long len, +bool need_rmap_locks,bool for_stack); +#endif /* __MM_INTERNAL_H */
mm/mmap.c +81 -0
84 lines not on this page · raw message
Signature · 1 line
2.45.2
PATCH v4 4/7 mm: move internal core VMA manipulation functions to own file
In reply to Lorenzo StoakesThis patch introduces vma.c and moves internal core VMA manipulation functions to this file from mmap.c.
This allows us to isolate VMA functionality in a single place such that we can create userspace testing code that invokes this functionality in an environment where we can implement simple unit tests of core functionality.
This patch ensures that core VMA functionality is explicitly marked as such by its presence in mm/vma.h.
It also places the header includes required by vma.c in vma_internal.h, which is simply imported by vma.c. This makes the VMA functionality testable, as userland testing code can simply stub out functionality as required.
--- include/linux/mm.h | 35 - mm/Makefile | 2 +- mm/internal.h | 236 +----- mm/mmap.c | 1980 +++----------------------------------------- mm/mmu_notifier.c | 2 + mm/vma.c | 1766 +++++++++++++++++++++++++++++++++++++++ mm/vma.h | 364 ++++++++ mm/vma_internal.h | 50 ++ 8 files changed, 2292 insertions(+), 2143 deletions(-) create mode 100644 mm/vma.c create mode 100644 mm/vma.h create mode 100644 mm/vma_internal.h
include/linux/mm.h +0 -35
@@ -1005,21 +1005,6 @@ static inline struct vm_area_struct *vma_prev(struct vma_iterator *vmi)return mas_prev (&vmi->mas,0 ); } -static inline unsigned long vma_iter_addr (struct vma_iterator *vmi) -{ -return vmi->mas.index; -} - -static inline unsigned long vma_iter_end (struct vma_iterator *vmi) -{ -return vmi->mas.last +1 ; -} -static inline int vma_iter_bulk_alloc (struct vma_iterator *vmi, -unsigned long count) -{ -return mas_expected_entries (&vmi->mas, count); -} -static inline int vma_iter_clear_gfp (struct vma_iterator *vmi,unsigned long start,unsigned long end,gfp_t gfp) {
@@ -2544,21 +2529,6 @@ int get_cmdline(struct task_struct *task, char *buffer, int buflen);#define MM_CP_UFFD_WP_ALL (MM_CP_UFFD_WP | \ MM_CP_UFFD_WP_RESOLVE) -bool vma_needs_dirty_tracking (struct vm_area_struct *vma); -bool vma_wants_writenotify (struct vm_area_struct *vma,pgprot_t vm_page_prot); -static inline bool vma_wants_manual_pte_write_upgrade (struct vm_area_struct *vma) -{ -/* -* We want to check manually if we can change individual PTEs writable -* if we can't do that automatically for all PTEs in a mapping. For -* private mappings, that's always the case when we have write -* permissions as we properly have to handle COW. -*/ -if (vma->vm_flags &VM_SHARED ) -return vma_wants_writenotify (vma, vma->vm_page_prot); -return !!(vma->vm_flags &VM_WRITE ); - -}bool can_change_pte_writable (struct vm_area_struct *vma,unsigned long addr,pte_t pte); extern long change_protection(struct mmu_gather *tlb,
@@ -3255,12 +3225,7 @@ void anon_vma_interval_tree_verify(struct anon_vma_chain *node);/* mmap.c */ extern int __vm_enough_memory (struct mm_struct *mm,long pages,int cap_sys_admin); -extern struct anon_vma *find_mergeable_anon_vma (struct vm_area_struct *);extern int insert_vm_struct (struct mm_struct *,struct vm_area_struct *); -extern void unlink_file_vma (struct vm_area_struct *); -extern struct vm_area_struct *copy_vma (struct vm_area_struct **, -unsigned long addr,unsigned long len,pgoff_t pgoff, -bool *need_rmap_locks);extern void exit_mmap (struct mm_struct *);int relocate_vma_down (struct vm_area_struct *vma,unsigned long shift);
mm/Makefile +1 -1
@@ -37,7 +37,7 @@ mmu-y := nommu.o mmu-$(CONFIG_MMU) := highmem.o memory.o mincore.o \ mlock.o mmap.o mmu_gather.o mprotect.o mremap.o \ msync.o page_vma_mapped.o pagewalk.o \ - pgtable-generic.o rmap.o vmalloc.o + pgtable-generic.o rmap.o vmalloc.o vma.o ifdef CONFIG_CROSS_MEMORY_ATTACH
mm/internal.h +5 -231
273 lines not on this page · raw message
mm/mmap.c +104 -1876
2,057 lines not on this page · raw message
mm/mmu_notifier.c +2 -0
@@ -19,6 +19,8 @@#include <linux/sched/mm.h> #include <linux/slab.h> +#include "vma.h" +/* global SRCU for all MMs */ DEFINE_STATIC_SRCU (srcu);
mm/vma.c new file +1766 -0
600 lines not on this page · raw message
mm/vma.h new file +364 -0
364 lines not on this page · raw message
mm/vma_internal.h new file +50 -0
50 lines not on this page · raw message
The rest of this diff is not shown. View the raw message.
Signature · 1 line
2.45.2
Part of the diff is not shown here. View the raw message.
PATCH v4 5/7 MAINTAINERS: Add entry for new VMA files
In reply to Lorenzo StoakesThe vma files contain logic split from mmap.c for the most part and are all relevant to VMA logic, so maintain the same reviewers for both.
--- MAINTAINERS | 13 +++++++++++++ 1 file changed, 13 insertions(+)
MAINTAINERS +13 -0
@@ -24383,6 +24383,19 @@ F: include/uapi/linux/vsockmon.h F: net/vmw_vsock/ F: tools/testing/vsock/ +VMA +M: Andrew Morton <[email protected]> +R: Liam R. Howlett <[email protected]> +R: Vlastimil Babka <[email protected]> +R: Lorenzo Stoakes <[email protected]> +L: [email protected] +S: Maintained +W: https://www.linux-mm.org +T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm +F: mm/vma.c +F: mm/vma.h +F: mm/vma_internal.h + VMALLOC M: Andrew Morton <[email protected]> R: Uladzislau Rezki <[email protected]>
Signature · 1 line
2.45.2
PATCH v4 6/7 tools: separate out shared radix-tree components
In reply to Lorenzo StoakesThe core components contained within the radix-tree tests which provide shims for kernel headers and access to the maple tree are useful for testing other things, so separate them out and make the radix tree tests dependent on the shared components.
This lays the groundwork for us to add VMA tests of the newly introduced vma.c file.
---
tools/testing/radix-tree/.gitignore | 1 +
tools/testing/radix-tree/Makefile | 72 ++++---------------
tools/testing/radix-tree/xarray.c | 10 +--
.../generated => shared}/autoconf.h | 0
tools/testing/{radix-tree => shared}/linux.c | 0
.../{radix-tree => shared}/linux/bug.h | 0
.../{radix-tree => shared}/linux/cpu.h | 0
.../{radix-tree => shared}/linux/idr.h | 0
.../{radix-tree => shared}/linux/init.h | 0
.../{radix-tree => shared}/linux/kconfig.h | 0
.../{radix-tree => shared}/linux/kernel.h | 0
.../{radix-tree => shared}/linux/kmemleak.h | 0
.../{radix-tree => shared}/linux/local_lock.h | 0
.../{radix-tree => shared}/linux/lockdep.h | 0
.../{radix-tree => shared}/linux/maple_tree.h | 0
.../{radix-tree => shared}/linux/percpu.h | 0
.../{radix-tree => shared}/linux/preempt.h | 0
.../{radix-tree => shared}/linux/radix-tree.h | 0
.../{radix-tree => shared}/linux/rcupdate.h | 0
.../{radix-tree => shared}/linux/xarray.h | 0
tools/testing/shared/maple-shared.h | 9 +++
tools/testing/shared/maple-shim.c | 7 ++
tools/testing/shared/shared.h | 33 +++++++++
tools/testing/shared/shared.mk | 72 +++++++++++++++++++
.../trace/events/maple_tree.h | 0
tools/testing/shared/xarray-shared.c | 5 ++
tools/testing/shared/xarray-shared.h | 4 ++
27 files changed, 144 insertions(+), 69 deletions(-)
rename tools/testing/{radix-tree/generated => shared}/autoconf.h (100%)
rename tools/testing/{radix-tree => shared}/linux.c (100%)
rename tools/testing/{radix-tree => shared}/linux/bug.h (100%)
rename tools/testing/{radix-tree => shared}/linux/cpu.h (100%)
rename tools/testing/{radix-tree => shared}/linux/idr.h (100%)
rename tools/testing/{radix-tree => shared}/linux/init.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kconfig.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kernel.h (100%)
rename tools/testing/{radix-tree => shared}/linux/kmemleak.h (100%)
rename tools/testing/{radix-tree => shared}/linux/local_lock.h (100%)
rename tools/testing/{radix-tree => shared}/linux/lockdep.h (100%)
rename tools/testing/{radix-tree => shared}/linux/maple_tree.h (100%)
rename tools/testing/{radix-tree => shared}/linux/percpu.h (100%)
rename tools/testing/{radix-tree => shared}/linux/preempt.h (100%)
rename tools/testing/{radix-tree => shared}/linux/radix-tree.h (100%)
rename tools/testing/{radix-tree => shared}/linux/rcupdate.h (100%)
rename tools/testing/{radix-tree => shared}/linux/xarray.h (100%)
create mode 100644 tools/testing/shared/maple-shared.h
create mode 100644 tools/testing/shared/maple-shim.c
create mode 100644 tools/testing/shared/shared.h
create mode 100644 tools/testing/shared/shared.mk
rename tools/testing/{radix-tree => shared}/trace/events/maple_tree.h (100%)
create mode 100644 tools/testing/shared/xarray-shared.c
create mode 100644 tools/testing/shared/xarray-shared.htools/testing/radix-tree/.gitignore +1 -0
@@ -1,4 +1,5 @@ # SPDX-License-Identifier: GPL-2.0-only +generated/autoconf.h generated/bit-length.h generated/map-shift.h idr.c
tools/testing/radix-tree/Makefile +12 -60
89 lines not on this page · raw message
tools/testing/radix-tree/xarray.c +1 -9
@@ -4,17 +4,9 @@* Copyright (c) 2018 Matthew Wilcox <[email protected]> */ -#define XA_DEBUG +#include "xarray-shared.h" #include "test.h" -#define module_init (x) -#define module_exit (x) -#define MODULE_AUTHOR (x) -#define MODULE_DESCRIPTION (X ) -#define MODULE_LICENSE (x) -#define dump_stack () assert(0) - -#include "../../../lib/xarray.c" #undef XA_DEBUG#include "../../../lib/test_xarray.c"
tools/testing/shared/autoconf.h renamed from tools/testing/radix-tree/generated/autoconf.h +0 -0
tools/testing/shared/linux.c renamed from tools/testing/radix-tree/linux.c +0 -0
tools/testing/shared/linux/bug.h renamed from tools/testing/radix-tree/linux/bug.h +0 -0
tools/testing/shared/linux/cpu.h renamed from tools/testing/radix-tree/linux/cpu.h +0 -0
tools/testing/shared/linux/idr.h renamed from tools/testing/radix-tree/linux/idr.h +0 -0
tools/testing/shared/linux/init.h renamed from tools/testing/radix-tree/linux/init.h +0 -0
tools/testing/shared/linux/kconfig.h renamed from tools/testing/radix-tree/linux/kconfig.h +0 -0
tools/testing/shared/linux/kernel.h renamed from tools/testing/radix-tree/linux/kernel.h +0 -0
tools/testing/shared/linux/kmemleak.h renamed from tools/testing/radix-tree/linux/kmemleak.h +0 -0
tools/testing/shared/linux/local_lock.h renamed from tools/testing/radix-tree/linux/local_lock.h +0 -0
tools/testing/shared/linux/lockdep.h renamed from tools/testing/radix-tree/linux/lockdep.h +0 -0
tools/testing/shared/linux/maple_tree.h renamed from tools/testing/radix-tree/linux/maple_tree.h +0 -0
tools/testing/shared/linux/percpu.h renamed from tools/testing/radix-tree/linux/percpu.h +0 -0
tools/testing/shared/linux/preempt.h renamed from tools/testing/radix-tree/linux/preempt.h +0 -0
tools/testing/shared/linux/radix-tree.h renamed from tools/testing/radix-tree/linux/radix-tree.h +0 -0
tools/testing/shared/linux/rcupdate.h renamed from tools/testing/radix-tree/linux/rcupdate.h +0 -0
tools/testing/shared/linux/xarray.h renamed from tools/testing/radix-tree/linux/xarray.h +0 -0
tools/testing/shared/maple-shared.h new file +9 -0
@@ -0,0 +1,9 @@ +/* SPDX-License-Identifier: GPL-2.0+ */ + +#define CONFIG_DEBUG_MAPLE_TREE +#define CONFIG_MAPLE_SEARCH +#define MAPLE_32BIT (MAPLE_NODE_SLOTS > 31) +#include "shared.h" +#include <stdlib.h> +#include <time.h> +#include "linux/init.h"
tools/testing/shared/maple-shim.c new file +7 -0
@@ -0,0 +1,7 @@ +// SPDX-License-Identifier: GPL-2.0-or-later + +/* Very simple shim around the maple tree. */ + +#include "maple-shared.h" + +#include "../../../lib/maple_tree.c"
tools/testing/shared/shared.h new file +33 -0
@@ -0,0 +1,33 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#include <linux/types.h> +#include <linux/bug.h> +#include <linux/kernel.h> +#include <linux/bitops.h> + +#include <linux/gfp.h> +#include <linux/rcupdate.h> + +#ifndef module_init +#define module_init (x) +#endif + +#ifndef module_exit +#define module_exit (x) +#endif + +#ifndef MODULE_AUTHOR +#define MODULE_AUTHOR (x) +#endif + +#ifndef MODULE_LICENSE +#define MODULE_LICENSE (x) +#endif + +#ifndef MODULE_DESCRIPTION +#define MODULE_DESCRIPTION (x) +#endif + +#ifndef dump_stack +#define dump_stack () assert(0) +#endif
tools/testing/shared/shared.mk new file +72 -0
72 lines not on this page · raw message
tools/testing/shared/trace/events/maple_tree.h renamed from tools/testing/radix-tree/trace/events/maple_tree.h +0 -0
tools/testing/shared/xarray-shared.c new file +5 -0
@@ -0,0 +1,5 @@ +// SPDX-License-Identifier: GPL-2.0-or-later + +#include "xarray-shared.h" + +#include "../../../lib/xarray.c"
tools/testing/shared/xarray-shared.h new file +4 -0
@@ -0,0 +1,4 @@ +/* SPDX-License-Identifier: GPL-2.0+ */ + +#define XA_DEBUG +#include "shared.h"
Signature · 1 line
2.45.2
PATCH v4 7/7 tools: add skeleton code for userland testing of VMA logic
In reply to Lorenzo StoakesEstablish a new userland VMA unit testing implementation under tools/testing which utilises existing logic providing maple tree support in userland utilising the now-shared code previously exclusive to radix tree testing.
This provides fundamental VMA operations whose API is defined in mm/vma.h, while stubbing out superfluous functionality.
This exists as a proof-of-concept, with the test implementation functional and sufficient to allow userland compilation of vma.c, but containing only cursory tests to demonstrate basic functionality.
--- MAINTAINERS | 1 + tools/testing/vma/.gitignore | 7 + tools/testing/vma/Makefile | 16 + tools/testing/vma/linux/atomic.h | 12 + tools/testing/vma/linux/mmzone.h | 38 ++ tools/testing/vma/vma.c | 207 ++++++++ tools/testing/vma/vma_internal.h | 882 +++++++++++++++++++++++++++++++ 7 files changed, 1163 insertions(+) create mode 100644 tools/testing/vma/.gitignore create mode 100644 tools/testing/vma/Makefile create mode 100644 tools/testing/vma/linux/atomic.h create mode 100644 tools/testing/vma/linux/mmzone.h create mode 100644 tools/testing/vma/vma.c create mode 100644 tools/testing/vma/vma_internal.h
MAINTAINERS +1 -0
@@ -24395,6 +24395,7 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm F: mm/vma.c F: mm/vma.h F: mm/vma_internal.h +F: tools/testing/vma/ VMALLOC M: Andrew Morton <[email protected]>
tools/testing/vma/.gitignore new file +7 -0
@@ -0,0 +1,7 @@ +# SPDX-License-Identifier: GPL-2.0-only +generated/bit-length.h +generated/map-shift.h +generated/autoconf.h +idr.c +radix-tree.c +vma
tools/testing/vma/Makefile new file +16 -0
@@ -0,0 +1,16 @@ +# SPDX-License-Identifier: GPL-2.0-or-later + +.PHONY: default + +default: vma + +include ../shared/shared.mk + +OFILES = $(SHARED_OFILES) vma.o maple-shim.o +TARGETS = vma + +vma: $(OFILES) vma_internal.h ../../../mm/vma.c ../../../mm/vma.h + $(CC) $(CFLAGS) -o $@ $(OFILES) $(LDLIBS) + +clean: + $(RM) $(TARGETS) *.o radix-tree.c idr.c generated/map-shift.h generated/bit-length.h generated/autoconf.h
tools/testing/vma/linux/atomic.h new file +12 -0
@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0-or-later */ + +#ifndef _LINUX_ATOMIC_H +#define _LINUX_ATOMIC_H + +#define atomic_t int32_t +#define atomic_inc (x) uatomic_inc(x) +#define atomic_read (x) uatomic_read(x) +#define atomic_set (x, y) do {} while (0) +#define U8_MAX UCHAR_MAX + +#endif /* _LINUX_ATOMIC_H */
tools/testing/vma/linux/mmzone.h new file +38 -0
@@ -0,0 +1,38 @@ +/* SPDX-License-Identifier: GPL-2.0-or-later */ + +#ifndef _LINUX_MMZONE_H +#define _LINUX_MMZONE_H + +#include <linux/atomic.h> + +struct pglist_data *first_online_pgdat (void ); +struct pglist_data *next_online_pgdat (struct pglist_data *pgdat); + +#define for_each_online_pgdat (pgdat) \ + for (pgdat = first_online_pgdat(); \ + pgdat; \ + pgdat = next_online_pgdat(pgdat)) + +enum zone_type { + __MAX_NR_ZONES +}; + +#define MAX_NR_ZONES __MAX_NR_ZONES +#define MAX_PAGE_ORDER 10 +#define MAX_ORDER_NR_PAGES (1 << MAX_PAGE_ORDER) + +#define pageblock_order MAX_PAGE_ORDER +#define pageblock_nr_pages BIT(pageblock_order) +#define pageblock_align (pfn) ALIGN((pfn), pageblock_nr_pages) +#define pageblock_start_pfn (pfn) ALIGN_DOWN((pfn), pageblock_nr_pages) + +struct zone { +atomic_long_t managed_pages; +}; + +typedef struct pglist_data { +struct zone node_zones[MAX_NR_ZONES ]; + +}pg_data_t ; + +#endif /* _LINUX_MMZONE_H */
tools/testing/vma/vma.c new file +207 -0
207 lines not on this page · raw message
tools/testing/vma/vma_internal.h new file +882 -0
882 lines not on this page · raw message
Signature · 1 line
2.45.2