[syzbot] KASAN: slab-out-of-bounds Read in ntfs_listxattr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8ed710da2873 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10027d97880000
kernel config: https://syzkaller.appspot.com/x/.config?x=50de433dd4debef8
dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160e0797880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf79d5880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/75851d210874/disk-8ed710da.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c70846514634/vmlinux-8ed710da.xz
kernel image: https://storage.googleapis.com/syzbot-assets/34393d745af1/bzImage-8ed710da.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ce942d5850e5/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9fcea5...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:191 [inline]
BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710
Read of size 1 at addr ffff888021acaf3d by task syz-executor128/3632

CPU: 1 PID: 3632 Comm: syz-executor128 Not tainted 6.1.0-rc8-syzkaller-00014-g8ed710da2873 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description+0x74/0x340 mm/kasan/report.c:284
print_report+0x107/0x220 mm/kasan/report.c:395
kasan_report+0x139/0x170 mm/kasan/report.c:495
ntfs_list_ea fs/ntfs3/xattr.c:191 [inline]
ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710
vfs_listxattr fs/xattr.c:457 [inline]
listxattr+0x293/0x2d0 fs/xattr.c:804
path_listxattr fs/xattr.c:828 [inline]
__do_sys_llistxattr fs/xattr.c:846 [inline]
__se_sys_llistxattr fs/xattr.c:843 [inline]
__x64_sys_llistxattr+0x174/0x230 fs/xattr.c:843
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbd70b66749
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff05b9d818 EFLAGS: 00000246 ORIG_RAX: 00000000000000c3
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007fbd70b66749
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200000c0
RBP: 00007fbd70b25fe0 R08: 000000000001f6fe R09: 0000000000000000
R10: 00007fff05b9d6e0 R11: 0000000000000246 R12: 00007fbd70b26070
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>

Allocated by task 3632:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4c/0x70 mm/kasan/common.c:52
____kasan_kmalloc mm/kasan/common.c:371 [inline]
__kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:955 [inline]
__kmalloc+0xaf/0x1a0 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
ntfs_read_ea+0x437/0x820 fs/ntfs3/xattr.c:110
ntfs_list_ea fs/ntfs3/xattr.c:168 [inline]
ntfs_listxattr+0x184/0x570 fs/ntfs3/xattr.c:710
vfs_listxattr fs/xattr.c:457 [inline]
listxattr+0x293/0x2d0 fs/xattr.c:804
path_listxattr fs/xattr.c:828 [inline]
__do_sys_llistxattr fs/xattr.c:846 [inline]
__se_sys_llistxattr fs/xattr.c:843 [inline]
__x64_sys_llistxattr+0x174/0x230 fs/xattr.c:843
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

The buggy address belongs to the object at ffff888021acaf00
which belongs to the cache kmalloc-64 of size 64
The buggy address is located 61 bytes inside of
64-byte region [ffff888021acaf00, ffff888021acaf40)

The buggy address belongs to the physical page:
page:ffffea000086b280 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888021aca080 pfn:0x21aca
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 ffffea0000796a40 dead000000000005 ffff888012841640
raw: ffff888021aca080 000000008020001d 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY), pid 46, tgid 46 (kworker/u4:3), ts 7050450825, free_ts 6956530319
prep_new_page mm/page_alloc.c:2539 [inline]
get_page_from_freelist+0x72b/0x7a0 mm/page_alloc.c:4291
__alloc_pages+0x259/0x560 mm/page_alloc.c:5558
alloc_slab_page+0xbd/0x190 mm/slub.c:1794
allocate_slab+0x5e/0x4b0 mm/slub.c:1939
new_slab mm/slub.c:1992 [inline]
___slab_alloc+0x7f4/0xeb0 mm/slub.c:3180
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
__kmem_cache_alloc_node+0x252/0x310 mm/slub.c:3437
kmalloc_node_trace+0x23/0x60 mm/slab_common.c:1058
kmalloc_node include/linux/slab.h:575 [inline]
kzalloc_node include/linux/slab.h:700 [inline]
__get_vm_area_node+0x13f/0x380 mm/vmalloc.c:2494
__vmalloc_node_range+0x3a6/0x1400 mm/vmalloc.c:3173
alloc_thread_stack_node+0x307/0x500 kernel/fork.c:311
dup_task_struct+0x8b/0x490 kernel/fork.c:974
copy_process+0x637/0x3fc0 kernel/fork.c:2084
kernel_clone+0x227/0x640 kernel/fork.c:2671
user_mode_thread+0x12d/0x190 kernel/fork.c:2747
call_usermodehelper_exec_work+0x57/0x220 kernel/umh.c:175
process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1459 [inline]
free_pcp_prepare+0x80c/0x8f0 mm/page_alloc.c:1509
free_unref_page_prepare mm/page_alloc.c:3387 [inline]
free_unref_page+0x7d/0x630 mm/page_alloc.c:3483
__vunmap+0x867/0x9d0 mm/vmalloc.c:2713
free_work+0x66/0x90 mm/vmalloc.c:97
process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

Memory state around the buggy address:
ffff888021acae00: 00 00 00 00 01 fc fc fc fc fc fc fc fc fc fc fc
ffff888021acae80: 00 00 00 00 01 fc fc fc fc fc fc fc fc fc fc fc
>ffff888021acaf00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
^
ffff888021acaf80: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
ffff888021acb000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[Zeng Heng]

#syz fix: [PATCH] ntfs: fix panic about slab-out-of-bounds caused by
ntfs_listxattr()

[Dmitry Vyukov]

Fix up the title ([PATCH] is removed before committing to git + avoid
line wrap):

#syz fix:

[syzbot]

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: out-of-bounds Write in end_buffer_read_sync

==================================================================
BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:102 [inline]
BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline]
BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:320 [inline]
BUG: KASAN: out-of-bounds in end_buffer_read_sync+0xbd/0xd0 fs/buffer.c:160
Write of size 4 at addr ffffc90005177860 by task ksoftirqd/0/15

CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.0-rc8-syzkaller-00019-g6c46867c33fc #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description+0x74/0x340 mm/kasan/report.c:284
print_report+0x107/0x220 mm/kasan/report.c:395
kasan_report+0x139/0x170 mm/kasan/report.c:495

kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189
instrument_atomic_read_write include/linux/instrumented.h:102 [inline]
atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline]
put_bh include/linux/buffer_head.h:320 [inline]
end_buffer_read_sync+0xbd/0xd0 fs/buffer.c:160
end_bio_bh_io_sync+0xb1/0x110 fs/buffer.c:2655
req_bio_endio block/blk-mq.c:762 [inline]
blk_update_request+0x51c/0x1040 block/blk-mq.c:894
blk_mq_end_request+0x39/0x70 block/blk-mq.c:1021
blk_complete_reqs block/blk-mq.c:1099 [inline]
blk_done_softirq+0x119/0x160 block/blk-mq.c:1104
__do_softirq+0x277/0x75b kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x533/0xa10 kernel/smpboot.c:164

kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

</TASK>

The buggy address belongs to the virtual mapping at
[ffffc90005170000, ffffc90005179000) created by:
dup_task_struct+0x8b/0x490 kernel/fork.c:974

The buggy address belongs to the physical page:

page:ffffea0000a1ee40 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x287b9
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000

page dumped because: kasan: bad access detected
page_owner tracks the page as allocated

page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 4094, tgid 4094 (syz-executor.0), ts 124035664175, free_ts 123777583212

prep_new_page mm/page_alloc.c:2539 [inline]
get_page_from_freelist+0x72b/0x7a0 mm/page_alloc.c:4291
__alloc_pages+0x259/0x560 mm/page_alloc.c:5558

vm_area_alloc_pages mm/vmalloc.c:2975 [inline]
__vmalloc_area_node mm/vmalloc.c:3043 [inline]
__vmalloc_node_range+0x9b2/0x1400 mm/vmalloc.c:3213

alloc_thread_stack_node+0x307/0x500 kernel/fork.c:311
dup_task_struct+0x8b/0x490 kernel/fork.c:974
copy_process+0x637/0x3fc0 kernel/fork.c:2084
kernel_clone+0x227/0x640 kernel/fork.c:2671

__do_sys_clone kernel/fork.c:2812 [inline]
__se_sys_clone kernel/fork.c:2796 [inline]
__x64_sys_clone+0x276/0x2e0 kernel/fork.c:2796

do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1459 [inline]
free_pcp_prepare+0x80c/0x8f0 mm/page_alloc.c:1509
free_unref_page_prepare mm/page_alloc.c:3387 [inline]

free_unref_page_list+0xb4/0x7b0 mm/page_alloc.c:3529
release_pages+0x233a/0x25d0 mm/swap.c:1055
__pagevec_release+0x7d/0xf0 mm/swap.c:1075
pagevec_release include/linux/pagevec.h:71 [inline]
folio_batch_release include/linux/pagevec.h:135 [inline]
truncate_inode_pages_range+0x4a2/0x1830 mm/truncate.c:373
kill_bdev block/bdev.c:76 [inline]
blkdev_flush_mapping+0x153/0x2c0 block/bdev.c:662
blkdev_put_whole block/bdev.c:693 [inline]
blkdev_put+0x4a5/0x730 block/bdev.c:953
blkdev_close+0x55/0x80 block/fops.c:499
__fput+0x3ba/0x880 fs/file_table.c:320
task_work_run+0x243/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0x134/0x160 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xad/0x110 kernel/entry/common.c:203
__syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
syscall_exit_to_user_mode+0x2e/0x60 kernel/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:

ffffc90005177700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90005177780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90005177800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
^
ffffc90005177880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90005177900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


Tested on:

commit: 6c46867c ntfs: fix panic about slab-out-of-bounds caus..
git tree: https://github.com/henryZe/linux.git fix_ntfs_listxattr
console output: https://syzkaller.appspot.com/x/log.txt?x=12fa05f5880000

kernel config: https://syzkaller.appspot.com/x/.config?x=50de433dd4debef8
dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.

[syzbot]

This bug is marked as fixed by commit:
ntfs: fix panic about slab-out-of-bounds caused by ntfs_listxattr()

But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:

#syz fix: exact-commit-title

Until then the bug is still considered open and new crashes with
the same signature are ignored.

Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334

---
[1] I expect the commit to be present in:

1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git

2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git

The full list of 10 trees can be found at
https://syzkaller.appspot.com/upstream/repos

[syzbot]

[syzbot]

[syzbot]

[syzbot]

[syzbot]

> 在 2022/12/7 15:00, syzbot 写道:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 8ed710da2873 Merge tag 'arm64-fixes' of git://git.kernel.o..
>> git tree: upstream
>> console+strace: https://syzkaller.appspot.com/x/log.txt?x=10027d97880000

>> kernel config: https://syzkaller.appspot.com/x/.config?x=50de433dd4debef8
>> dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334
>> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160e0797880000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf79d5880000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/75851d210874/disk-8ed710da.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/c70846514634/vmlinux-8ed710da.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/34393d745af1/bzImage-8ed710da.xz
>> mounted in repro: https://storage.googleapis.com/syzbot-assets/ce942d5850e5/mount_0.gz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+9fcea5...@syzkaller.appspotmail.com
>>
>> loop0: detected capacity change from 0 to 4096
>> ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
>> ==================================================================
>> BUG: KASAN: slab-out-of-bounds in ntfs_list_ea fs/ntfs3/xattr.c:191 [inline]
>> BUG: KASAN: slab-out-of-bounds in ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710
>> Read of size 1 at addr ffff888021acaf3d by task syz-executor128/3632
>>

>> CPU: 1 PID: 3632 Comm: syz-executor128 Not tainted 6.1.0-rc8-syzkaller-00014-g8ed710da2873 #0

>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
>> Call Trace:
>> <TASK>
>> __dump_stack lib/dump_stack.c:88 [inline]
>> dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
>> print_address_description+0x74/0x340 mm/kasan/report.c:284
>> print_report+0x107/0x220 mm/kasan/report.c:395
>> kasan_report+0x139/0x170 mm/kasan/report.c:495

>> ntfs_list_ea fs/ntfs3/xattr.c:191 [inline]
>> ntfs_listxattr+0x401/0x570 fs/ntfs3/xattr.c:710
>> vfs_listxattr fs/xattr.c:457 [inline]
>> listxattr+0x293/0x2d0 fs/xattr.c:804
>> path_listxattr fs/xattr.c:828 [inline]
>> __do_sys_llistxattr fs/xattr.c:846 [inline]
>> __se_sys_llistxattr fs/xattr.c:843 [inline]
>> __x64_sys_llistxattr+0x174/0x230 fs/xattr.c:843

>> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
>> entry_SYSCALL_64_after_hwframe+0x63/0xcd

>> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
>> entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>

>> The buggy address belongs to the object at ffff888021acaf00
>> which belongs to the cache kmalloc-64 of size 64
>> The buggy address is located 61 bytes inside of
>> 64-byte region [ffff888021acaf00, ffff888021acaf40)
>>

>> The buggy address belongs to the physical page:

>> page:ffffea000086b280 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888021aca080 pfn:0x21aca
>> flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
>> raw: 00fff00000000200 ffffea0000796a40 dead000000000005 ffff888012841640

>> raw: ffff888021aca080 000000008020001d 00000001ffffffff 0000000000000000

>> page dumped because: kasan: bad access detected
>> page_owner tracks the page as allocated

>> page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY), pid 46, tgid 46 (kworker/u4:3), ts 7050450825, free_ts 6956530319

>> prep_new_page mm/page_alloc.c:2539 [inline]
>> get_page_from_freelist+0x72b/0x7a0 mm/page_alloc.c:4291
>> __alloc_pages+0x259/0x560 mm/page_alloc.c:5558

>> alloc_slab_page+0xbd/0x190 mm/slub.c:1794
>> allocate_slab+0x5e/0x4b0 mm/slub.c:1939
>> new_slab mm/slub.c:1992 [inline]
>> ___slab_alloc+0x7f4/0xeb0 mm/slub.c:3180
>> __slab_alloc mm/slub.c:3279 [inline]
>> slab_alloc_node mm/slub.c:3364 [inline]
>> __kmem_cache_alloc_node+0x252/0x310 mm/slub.c:3437
>> kmalloc_node_trace+0x23/0x60 mm/slab_common.c:1058
>> kmalloc_node include/linux/slab.h:575 [inline]
>> kzalloc_node include/linux/slab.h:700 [inline]
>> __get_vm_area_node+0x13f/0x380 mm/vmalloc.c:2494
>> __vmalloc_node_range+0x3a6/0x1400 mm/vmalloc.c:3173

>> alloc_thread_stack_node+0x307/0x500 kernel/fork.c:311
>> dup_task_struct+0x8b/0x490 kernel/fork.c:974
>> copy_process+0x637/0x3fc0 kernel/fork.c:2084
>> kernel_clone+0x227/0x640 kernel/fork.c:2671

>> user_mode_thread+0x12d/0x190 kernel/fork.c:2747
>> call_usermodehelper_exec_work+0x57/0x220 kernel/umh.c:175
>> process_one_work+0x81c/0xd10 kernel/workqueue.c:2289

>> page last free stack trace:
>> reset_page_owner include/linux/page_owner.h:24 [inline]
>> free_pages_prepare mm/page_alloc.c:1459 [inline]
>> free_pcp_prepare+0x80c/0x8f0 mm/page_alloc.c:1509
>> free_unref_page_prepare mm/page_alloc.c:3387 [inline]

>> free_unref_page+0x7d/0x630 mm/page_alloc.c:3483
>> __vunmap+0x867/0x9d0 mm/vmalloc.c:2713
>> free_work+0x66/0x90 mm/vmalloc.c:97
>> process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
>> worker_thread+0xb14/0x1330 kernel/workqueue.c:2436

>> kthread+0x266/0x300 kernel/kthread.c:376
>> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
>>

>> Memory state around the buggy address:

>> ffff888021acae00: 00 00 00 00 01 fc fc fc fc fc fc fc fc fc fc fc
>> ffff888021acae80: 00 00 00 00 01 fc fc fc fc fc fc fc fc fc fc fc
>>> ffff888021acaf00: 00 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc
>> ^
>> ffff888021acaf80: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc
>> ffff888021acb000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>> ==================================================================
>>
>>
>> ---
>> This report is generated by a bot. It may contain errors.
>> See https://goo.gl/tpsmEJ for more information about syzbot.
>> syzbot engineers can be reached at syzk...@googlegroups.com.
>>
>> syzbot will keep track of this issue. See:
>> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
>> syzbot can test patches for this issue, for details see:
>> https://goo.gl/tpsmEJ#testing-patches
>

> #syz unfix

Your commands are accepted, but please keep syzkall...@googlegroups.com mailing list in CC next time. It serves as a history of what happened with each bug report. Thank you.

>
>

[syzbot]

syzbot has bisected this issue to:

commit 6e5be40d32fb1907285277c02e74493ed43d77fe
Author: Konstantin Komarov <almaz.ale...@paragon-software.com>
Date: Fri Aug 13 14:21:30 2021 +0000

fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1587a32a280000
start commit: 8ed710da2873 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1787a32a280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1387a32a280000
kernel config: https://syzkaller.appspot.com/x/.config?x=b83f3e90d74765ea
dashboard link: https://syzkaller.appspot.com/bug?extid=9fcea5ef6dc4dc72d334
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17e7ec29880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11829e23880000

Reported-by: syzbot+9fcea5...@syzkaller.appspotmail.com
Fixes: 6e5be40d32fb ("fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection