================================================================== 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:303 [inline] BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0x93/0xe0 fs/buffer.c:161 Write of size 4 at addr ffffc900037e7830 by task ksoftirqd/1/24 CPU: 1 UID: 0 PID: 24 Comm: ksoftirqd/1 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/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_write include/linux/instrumented.h:96 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline] put_bh include/linux/buffer_head.h:303 [inline] end_buffer_read_sync+0x93/0xe0 fs/buffer.c:161 end_bio_bh_io_sync+0xe8/0x140 fs/buffer.c:2776 bio_endio+0x6dc/0x820 block/bio.c:1646 blk_update_request+0x80f/0x17d0 block/blk-mq.c:925 blk_mq_end_request+0x5b/0x620 block/blk-mq.c:1053 lo_complete_rq+0x232/0x2f0 drivers/block/loop.c:386 blk_complete_reqs+0xb1/0xf0 block/blk-mq.c:1128 handle_softirqs+0x219/0x8f0 kernel/softirq.c:554 run_ksoftirqd kernel/softirq.c:928 [inline] run_ksoftirqd+0x3a/0x60 kernel/softirq.c:920 smpboot_thread_fn+0x664/0xa10 kernel/smpboot.c:164 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 The buggy address belongs to the virtual mapping at [ffffc900037e0000, ffffc900037e9000) created by: kernel_clone+0xfd/0x960 kernel/fork.c:2781 The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888077c84000 pfn:0x77c84 memcg:ffff88802e284302 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: ffff888077c84000 0000000000000000 00000001ffffffff ffff88802e284302 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 25093, tgid 25093 (syz.3.8688), ts 1191446439734, free_ts 1174356734888 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x2d1/0x350 mm/page_alloc.c:1500 prep_new_page mm/page_alloc.c:1508 [inline] get_page_from_freelist+0x1351/0x2e50 mm/page_alloc.c:3446 __alloc_pages_noprof+0x22b/0x2460 mm/page_alloc.c:4702 alloc_pages_mpol_noprof+0x275/0x610 mm/mempolicy.c:2263 vm_area_alloc_pages mm/vmalloc.c:3587 [inline] __vmalloc_area_node mm/vmalloc.c:3656 [inline] __vmalloc_node_range_noprof+0x6da/0x14e0 mm/vmalloc.c:3837 alloc_thread_stack_node kernel/fork.c:313 [inline] dup_task_struct kernel/fork.c:1113 [inline] copy_process+0x2f3b/0x8de0 kernel/fork.c:2204 kernel_clone+0xfd/0x960 kernel/fork.c:2781 __do_sys_clone3+0x1f5/0x270 kernel/fork.c:3085 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f page last free pid 5292 tgid 5292 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1101 [inline] free_unref_page+0x64a/0xe40 mm/page_alloc.c:2619 kasan_depopulate_vmalloc_pte+0x63/0x80 mm/kasan/shadow.c:408 apply_to_pte_range mm/memory.c:2797 [inline] apply_to_pmd_range mm/memory.c:2841 [inline] apply_to_pud_range mm/memory.c:2877 [inline] apply_to_p4d_range mm/memory.c:2913 [inline] __apply_to_page_range+0x798/0xdd0 mm/memory.c:2947 kasan_release_vmalloc+0xac/0xc0 mm/kasan/shadow.c:525 purge_vmap_node+0x3ec/0x920 mm/vmalloc.c:2209 __purge_vmap_area_lazy+0x9ca/0xc10 mm/vmalloc.c:2293 drain_vmap_area_work+0x27/0x40 mm/vmalloc.c:2327 process_one_work+0x9c8/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c4/0x3a0 kernel/kthread.c:389 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Memory state around the buggy address: ffffc900037e7700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900037e7780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900037e7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc900037e7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900037e7900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================