syzbot


KASAN: stack-out-of-bounds Read in xfs_buf_lock

Status: upstream: reported C repro on 2022/12/12 05:50
Reported-by: syzbot+0bc698a422b5e4ac988c@syzkaller.appspotmail.com
First crash: 66d, last: 2h52m

Cause bisection: introduced by (bisect log) :
commit 679a99495b8fda800037b25af8cd990eb7dd72c9
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Nov 29 10:21:41 2021 +0000

  xfs: factor out a xfs_setup_dax_always helper

Crash: INFO: task hung in unregister_shrinker (log)
Repro: C syz .config
Last patch testing requests:
Created Duration User Patch Repo Result
2023/01/23 08:21 23m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 7dd4b804e080 error

Sample crash report:
==================================================================
BUG: KASAN: stack-out-of-bounds in instrument_atomic_read include/linux/instrumented.h:72 [inline]
BUG: KASAN: stack-out-of-bounds in atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline]
BUG: KASAN: stack-out-of-bounds in xfs_buf_lock+0xd0/0x750 fs/xfs/xfs_buf.c:1118
Read of size 4 at addr ffffc9000654fbec by task syz-executor824/5676

CPU: 0 PID: 5676 Comm: syz-executor824 Not tainted 6.2.0-rc3-syzkaller-00021-g7dd4b804e080 #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+0xd1/0x138 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:306 [inline]
 print_report+0x15e/0x45d mm/kasan/report.c:417
 kasan_report+0xbf/0x1f0 mm/kasan/report.c:517
 check_region_inline mm/kasan/generic.c:183 [inline]
 kasan_check_range+0x141/0x190 mm/kasan/generic.c:189
 instrument_atomic_read include/linux/instrumented.h:72 [inline]
 atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline]
 xfs_buf_lock+0xd0/0x750 fs/xfs/xfs_buf.c:1118
 xfs_buf_delwri_submit_buffers+0x131/0xae0 fs/xfs/xfs_buf.c:2165
 xfs_buf_delwri_submit+0x8a/0x260 fs/xfs/xfs_buf.c:2243
 xfs_qm_shrink_scan fs/xfs/xfs_qm.c:522 [inline]
 xfs_qm_shrink_scan+0x1a7/0x370 fs/xfs/xfs_qm.c:503
 do_shrink_slab+0x464/0xce0 mm/vmscan.c:843
 shrink_slab+0x175/0x660 mm/vmscan.c:1003
 drop_slab_node mm/vmscan.c:1031 [inline]
 drop_slab+0x13a/0x2a0 mm/vmscan.c:1049
 drop_caches_sysctl_handler+0xfa/0x110 fs/drop_caches.c:66
 proc_sys_call_handler+0x49c/0x6d0 fs/proc/proc_sysctl.c:604
 call_write_iter include/linux/fs.h:2189 [inline]
 do_iter_readv_writev+0x20b/0x3b0 fs/read_write.c:735
 do_iter_write+0x182/0x700 fs/read_write.c:861
 vfs_iter_write+0x74/0xa0 fs/read_write.c:902
 iter_file_splice_write+0x745/0xc90 fs/splice.c:686
 do_splice_from fs/splice.c:764 [inline]
 direct_splice_actor+0x114/0x180 fs/splice.c:931
 splice_direct_to_actor+0x335/0x8a0 fs/splice.c:886
 do_splice_direct+0x1ab/0x280 fs/splice.c:974
 do_sendfile+0xb19/0x1270 fs/read_write.c:1255
 __do_sys_sendfile64 fs/read_write.c:1317 [inline]
 __se_sys_sendfile64 fs/read_write.c:1309 [inline]
 __x64_sys_sendfile64+0x14d/0x210 fs/read_write.c:1309
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd74df22779
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 01 18 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:00007ffe1c61a0e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00000000000114e9 RCX: 00007fd74df22779
RDX: 0000000020002080 RSI: 0000000000000004 RDI: 0000000000000005
RBP: 0000000000000000 R08: 00007ffe1c61a110 R09: 00007ffe1c61a110
R10: 0000000000000870 R11: 0000000000000246 R12: 00007ffe1c61a10c
R13: 00007ffe1c61a140 R14: 00007ffe1c61a120 R15: 000000000000000b
 </TASK>

The buggy address belongs to the virtual mapping at
 [ffffc90006548000, ffffc90006551000) created by:
 kernel_clone+0xeb/0x990 kernel/fork.c:2681

The buggy address belongs to the physical page:
page:ffffea00008d3f00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x234fc
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 0x2dc2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), pid 2, tgid 2 (kthreadd), ts 71883428260, free_ts 70232816920
 prep_new_page mm/page_alloc.c:2531 [inline]
 get_page_from_freelist+0x119c/0x2ce0 mm/page_alloc.c:4283
 __alloc_pages+0x1cb/0x5b0 mm/page_alloc.c:5549
 alloc_pages+0x1aa/0x270 mm/mempolicy.c:2286
 vm_area_alloc_pages mm/vmalloc.c:2989 [inline]
 __vmalloc_area_node mm/vmalloc.c:3057 [inline]
 __vmalloc_node_range+0x978/0x13c0 mm/vmalloc.c:3227
 alloc_thread_stack_node kernel/fork.c:311 [inline]
 dup_task_struct kernel/fork.c:987 [inline]
 copy_process+0x12d2/0x7520 kernel/fork.c:2097
 kernel_clone+0xeb/0x990 kernel/fork.c:2681
 kernel_thread+0xb9/0xf0 kernel/fork.c:2741
 create_kthread kernel/kthread.c:399 [inline]
 kthreadd+0x4f2/0x750 kernel/kthread.c:746
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1446 [inline]
 free_pcp_prepare+0x65c/0xc00 mm/page_alloc.c:1496
 free_unref_page_prepare mm/page_alloc.c:3369 [inline]
 free_unref_page_list+0x176/0xcd0 mm/page_alloc.c:3510
 release_pages+0xcb1/0x1330 mm/swap.c:1076
 tlb_batch_pages_flush+0xa8/0x1a0 mm/mmu_gather.c:97
 tlb_flush_mmu_free mm/mmu_gather.c:292 [inline]
 tlb_flush_mmu mm/mmu_gather.c:299 [inline]
 tlb_finish_mmu+0x14b/0x7e0 mm/mmu_gather.c:391
 exit_mmap+0x202/0x7b0 mm/mmap.c:3096
 __mmput+0x128/0x4c0 kernel/fork.c:1207
 mmput+0x60/0x70 kernel/fork.c:1229
 exit_mm kernel/exit.c:563 [inline]
 do_exit+0x9ac/0x2950 kernel/exit.c:854
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1012
 __do_sys_exit_group kernel/exit.c:1023 [inline]
 __se_sys_exit_group kernel/exit.c:1021 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1021
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
 ffffc9000654fa80: 00 00 00 00 00 f1 f1 f1 f1 00 00 f3 f3 00 00 00
 ffffc9000654fb00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000654fb80: 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 04
                                                          ^
 ffffc9000654fc00: f2 04 f2 00 f2 f2 f2 00 f3 f3 f3 00 00 00 00 00
 ffffc9000654fc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (15):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-root 2023/01/11 15:08 upstream 7dd4b804e080 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci2-upstream-fs 2023/02/05 09:20 upstream db27c22251e7 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2023/01/09 11:57 upstream 1fe4fd6f5cad 1dac8c7a .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2023/01/08 10:51 upstream 9b43a525db12 1dac8c7a .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2022/12/27 05:54 upstream 1b929c02afd3 9da18ae8 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2022/12/24 13:38 upstream 72a85e2b0a1e 9da18ae8 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-upstream-kasan-gce-selinux-root 2022/12/23 19:27 upstream 8395ae05cb5a 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2022/12/12 05:50 upstream 830b3c68c1fb 67be1ae7 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream 2022/12/07 01:50 upstream 8ed710da2873 d88f3abb .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2023/01/06 07:19 upstream 1f5abbd77e2c 1dac8c7a .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2023/01/03 03:45 upstream 69b41ac87e4a ab32d508 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2022/12/26 06:24 upstream 1b929c02afd3 9da18ae8 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2022/12/11 20:31 upstream 4cee37b3a4e6 67be1ae7 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2022/12/10 09:35 upstream 3ecc37918c80 67be1ae7 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
ci-qemu-upstream-386 2022/12/01 05:06 upstream 04aa64375f48 4c2a66e8 .config console log report info KASAN: stack-out-of-bounds Read in xfs_buf_lock
* Struck through repros no longer work on HEAD.