================================================================== BUG: KASAN: stack-out-of-bounds in instrument_atomic_read include/linux/instrumented.h:68 [inline] BUG: KASAN: stack-out-of-bounds in atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline] BUG: KASAN: stack-out-of-bounds in xfs_buf_lock+0x92/0x4b0 fs/xfs/xfs_buf.c:1124 Read of size 4 at addr ffffc900048a7b84 by task syz-executor.0/20364 CPU: 1 PID: 20364 Comm: syz-executor.0 Not tainted 6.8.0-rc7-syzkaller-00017-g29cd507cbec2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc4/0x620 mm/kasan/report.c:488 kasan_report+0xda/0x110 mm/kasan/report.c:601 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0xef/0x1a0 mm/kasan/generic.c:189 instrument_atomic_read include/linux/instrumented.h:68 [inline] atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline] xfs_buf_lock+0x92/0x4b0 fs/xfs/xfs_buf.c:1124 xfs_buf_delwri_submit_buffers+0x16e/0xa20 fs/xfs/xfs_buf.c:2210 xfs_buf_delwri_submit+0x8a/0x270 fs/xfs/xfs_buf.c:2288 xfs_qm_shrink_scan+0x209/0x3f0 fs/xfs/xfs_qm.c:521 do_shrink_slab+0x426/0x1120 mm/shrinker.c:435 shrink_slab+0x18a/0x1310 mm/shrinker.c:662 drop_slab_node mm/vmscan.c:387 [inline] drop_slab+0x14d/0x2c0 mm/vmscan.c:405 drop_caches_sysctl_handler+0x173/0x190 fs/drop_caches.c:68 proc_sys_call_handler+0x4cc/0x6f0 fs/proc/proc_sysctl.c:595 call_write_iter include/linux/fs.h:2087 [inline] iter_file_splice_write+0x908/0x10b0 fs/splice.c:743 do_splice_from fs/splice.c:941 [inline] direct_splice_actor+0x19b/0x6d0 fs/splice.c:1164 splice_direct_to_actor+0x347/0xa40 fs/splice.c:1108 do_splice_direct_actor fs/splice.c:1207 [inline] do_splice_direct+0x17e/0x250 fs/splice.c:1233 do_sendfile+0xaac/0xdb0 fs/read_write.c:1295 __do_sys_sendfile64 fs/read_write.c:1356 [inline] __se_sys_sendfile64 fs/read_write.c:1348 [inline] __x64_sys_sendfile64+0x155/0x220 fs/read_write.c:1348 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd5/0x270 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6f/0x77 RIP: 0033:0x7f5d86c7dda9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f5d87a1d0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007f5d86dac050 RCX: 00007f5d86c7dda9 RDX: 0000000020000180 RSI: 0000000000000003 RDI: 0000000000000004 RBP: 00007f5d86cca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000e15 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007f5d86dac050 R15: 00007fffa294add8 The buggy address belongs to the virtual mapping at [ffffc900048a0000, ffffc900048a9000) created by: kernel_clone+0xfd/0x930 kernel/fork.c:2902 The buggy address belongs to the physical page: page:ffffea0000eb38c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x3ace3 memcg:ffff888026c34802 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888026c34802 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 20304, tgid 20304 (syz-executor.4), ts 3040517767769, free_ts 3039820399044 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x2d4/0x350 mm/page_alloc.c:1533 prep_new_page mm/page_alloc.c:1540 [inline] get_page_from_freelist+0xa28/0x3780 mm/page_alloc.c:3311 __alloc_pages+0x22f/0x2440 mm/page_alloc.c:4567 alloc_pages_mpol+0x258/0x600 mm/mempolicy.c:2133 vm_area_alloc_pages mm/vmalloc.c:3063 [inline] __vmalloc_area_node mm/vmalloc.c:3139 [inline] __vmalloc_node_range+0xa6e/0x1540 mm/vmalloc.c:3320 alloc_thread_stack_node kernel/fork.c:307 [inline] dup_task_struct kernel/fork.c:1112 [inline] copy_process+0x150b/0x97b0 kernel/fork.c:2327 kernel_clone+0xfd/0x930 kernel/fork.c:2902 __do_sys_clone3+0x1f5/0x270 kernel/fork.c:3203 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd5/0x270 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6f/0x77 page last free pid 17391 tgid 17391 stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1140 [inline] free_unref_page_prepare+0x527/0xb10 mm/page_alloc.c:2346 free_unref_page+0x33/0x3c0 mm/page_alloc.c:2486 vfree+0x181/0x7a0 mm/vmalloc.c:2842 delayed_vfree_work+0x56/0x70 mm/vmalloc.c:2763 process_one_work+0x889/0x15e0 kernel/workqueue.c:2633 process_scheduled_works kernel/workqueue.c:2706 [inline] worker_thread+0x8b9/0x12a0 kernel/workqueue.c:2787 kthread+0x2c6/0x3b0 kernel/kthread.c:388 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:243 Memory state around the buggy address: ffffc900048a7a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900048a7b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 >ffffc900048a7b80: f1 f1 04 f2 04 f2 00 f3 f3 f3 00 00 00 00 00 00 ^ ffffc900048a7c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900048a7c80: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 f1 f1 04 f2 ==================================================================