================================================================== 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:306 [inline] BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0x8f/0xe0 fs/buffer.c:161 Write of size 4 at addr ffffc900047c7898 by task ksoftirqd/1/22 CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted 6.6.0-syzkaller-16159-g3ca112b71f35 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 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:364 [inline] print_report+0xc4/0x620 mm/kasan/report.c:475 kasan_report+0xda/0x110 mm/kasan/report.c:588 check_region_inline mm/kasan/generic.c:181 [inline] kasan_check_range+0xef/0x190 mm/kasan/generic.c:187 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:306 [inline] end_buffer_read_sync+0x8f/0xe0 fs/buffer.c:161 end_bio_bh_io_sync+0xdd/0x130 fs/buffer.c:2775 bio_endio+0x593/0x6a0 block/bio.c:1603 req_bio_endio block/blk-mq.c:788 [inline] blk_update_request+0x67b/0x1780 block/blk-mq.c:933 blk_mq_end_request+0x57/0x520 block/blk-mq.c:1056 lo_complete_rq+0x232/0x2f0 drivers/block/loop.c:370 blk_complete_reqs+0xb2/0xf0 block/blk-mq.c:1131 __do_softirq+0x21a/0x968 kernel/softirq.c:553 run_ksoftirqd kernel/softirq.c:921 [inline] run_ksoftirqd+0x31/0x60 kernel/softirq.c:913 smpboot_thread_fn+0x660/0xa00 kernel/smpboot.c:164 kthread+0x33c/0x440 kernel/kthread.c:388 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242 The buggy address belongs to the virtual mapping at [ffffc900047c0000, ffffc900047c9000) created by: kernel_clone+0xfd/0x920 kernel/fork.c:2907 The buggy address belongs to the physical page: page:ffffea000059ed00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x167b4 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() 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 5416, tgid 5416 (syz-executor.0), ts 356895576081, free_ts 356483140919 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x2cf/0x340 mm/page_alloc.c:1537 prep_new_page mm/page_alloc.c:1544 [inline] get_page_from_freelist+0xa25/0x36c0 mm/page_alloc.c:3312 __alloc_pages+0x1d0/0x4a0 mm/page_alloc.c:4568 alloc_pages_mpol+0x258/0x5f0 mm/mempolicy.c:2133 vm_area_alloc_pages mm/vmalloc.c:3063 [inline] __vmalloc_area_node mm/vmalloc.c:3139 [inline] __vmalloc_node_range+0x8f3/0x1bf0 mm/vmalloc.c:3320 alloc_thread_stack_node kernel/fork.c:309 [inline] dup_task_struct kernel/fork.c:1118 [inline] copy_process+0x13e3/0x74b0 kernel/fork.c:2332 kernel_clone+0xfd/0x920 kernel/fork.c:2907 __do_sys_clone+0xba/0x100 kernel/fork.c:3050 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1137 [inline] free_unref_page_prepare+0x4f8/0xa90 mm/page_alloc.c:2347 free_unref_page+0x33/0x3b0 mm/page_alloc.c:2487 mm_free_pgd kernel/fork.c:803 [inline] __mmdrop+0xd7/0x470 kernel/fork.c:919 mmdrop include/linux/sched/mm.h:54 [inline] mmdrop_sched include/linux/sched/mm.h:82 [inline] mmdrop_lazy_tlb_sched include/linux/sched/mm.h:109 [inline] finish_task_switch.isra.0+0x79d/0xca0 kernel/sched/core.c:5275 context_switch kernel/sched/core.c:5379 [inline] __schedule+0xeea/0x59a0 kernel/sched/core.c:6688 __schedule_loop kernel/sched/core.c:6763 [inline] schedule+0xe7/0x270 kernel/sched/core.c:6778 do_nanosleep+0x218/0x500 kernel/time/hrtimer.c:2047 hrtimer_nanosleep+0x1ae/0x440 kernel/time/hrtimer.c:2100 common_nsleep+0xa1/0xc0 kernel/time/posix-timers.c:1350 __do_sys_clock_nanosleep kernel/time/posix-timers.c:1396 [inline] __se_sys_clock_nanosleep kernel/time/posix-timers.c:1373 [inline] __x64_sys_clock_nanosleep+0x344/0x490 kernel/time/posix-timers.c:1373 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b Memory state around the buggy address: ffffc900047c7780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900047c7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900047c7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc900047c7900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900047c7980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================