================================================================== BUG: KASAN: stack-out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:96 [inline] BUG: KASAN: stack-out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline] BUG: KASAN: stack-out-of-bounds in put_bh include/linux/buffer_head.h:302 [inline] BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0xc3/0xe0 fs/buffer.c:161 Write of size 4 at addr ffffc9000d3a64a0 by task kworker/u4:10/1095 CPU: 0 UID: 0 PID: 1095 Comm: kworker/u4:10 Not tainted 6.16.0-syzkaller-12288-g2b38afce25c4 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Workqueue: loop0 loop_workfn Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline] put_bh include/linux/buffer_head.h:302 [inline] end_buffer_read_sync+0xc3/0xe0 fs/buffer.c:161 end_bio_bh_io_sync+0xba/0x120 fs/buffer.c:2776 blk_update_request+0x57e/0xe60 block/blk-mq.c:989 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1151 lo_rw_aio_complete drivers/block/loop.c:327 [inline] lo_rw_aio+0xd75/0xfa0 drivers/block/loop.c:401 do_req_filebacked drivers/block/loop.c:-1 [inline] loop_handle_cmd drivers/block/loop.c:1910 [inline] loop_process_work+0x835/0xf90 drivers/block/loop.c:1945 process_one_work kernel/workqueue.c:3236 [inline] process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3319 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400 kthread+0x70e/0x8a0 kernel/kthread.c:463 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 The buggy address belongs to a 8-page vmalloc region starting at 0xffffc9000d3a0000 allocated at copy_process+0x54b/0x3c00 kernel/fork.c:2004 The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x3f3c1 memcg:ffff88804314a202 flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff) raw: 04fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88804314a202 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_ZERO|__GFP_NOWARN), pid 5356, tgid 5356 (syz.0.0), ts 70741096646, free_ts 70693308647 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 alloc_frozen_pages_noprof mm/mempolicy.c:2487 [inline] alloc_pages_noprof+0xa9/0x190 mm/mempolicy.c:2507 vm_area_alloc_pages mm/vmalloc.c:3642 [inline] __vmalloc_area_node mm/vmalloc.c:3720 [inline] __vmalloc_node_range_noprof+0x97d/0x12f0 mm/vmalloc.c:3893 __vmalloc_node_noprof+0xc2/0x110 mm/vmalloc.c:3956 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct+0x3e7/0x860 kernel/fork.c:882 copy_process+0x54b/0x3c00 kernel/fork.c:2004 kernel_clone+0x21e/0x840 kernel/fork.c:2605 __do_sys_clone3 kernel/fork.c:2909 [inline] __se_sys_clone3+0x256/0x2d0 kernel/fork.c:2888 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f page last free pid 5358 tgid 5356 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1395 [inline] __free_frozen_pages+0xbc4/0xd30 mm/page_alloc.c:2895 drain_page_cache mm/slab_common.c:1494 [inline] kfree_rcu_shrink_scan+0xc9/0x130 mm/slab_common.c:2117 do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437 shrink_slab+0xd74/0x10d0 mm/shrinker.c:664 drop_slab_node mm/vmscan.c:441 [inline] drop_slab+0x14e/0x290 mm/vmscan.c:459 drop_caches_sysctl_handler+0xc7/0x170 fs/drop_caches.c:68 proc_sys_call_handler+0x509/0x7c0 fs/proc/proc_sysctl.c:600 do_iter_readv_writev+0x61c/0x8b0 fs/read_write.c:-1 vfs_writev+0x31a/0x960 fs/read_write.c:1057 do_writev+0x14d/0x2d0 fs/read_write.c:1103 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Memory state around the buggy address: ffffc9000d3a6380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000d3a6400: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 04 f2 00 00 >ffffc9000d3a6480: 00 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 f3 f3 f3 f3 ^ ffffc9000d3a6500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000d3a6580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================