================================================================== BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:96 [inline] BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline] BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:308 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0xc1/0xd0 fs/buffer.c:161 Write of size 4 at addr ffffc90009fcf740 by task ksoftirqd/1/22 CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted 6.6.0-rc3-syzkaller-00044-g633b47cb009d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0x163/0x540 mm/kasan/report.c:475 kasan_report+0x175/0x1b0 mm/kasan/report.c:588 kasan_check_range+0x27e/0x290 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:308 [inline] end_buffer_read_sync+0xc1/0xd0 fs/buffer.c:161 end_bio_bh_io_sync+0xb7/0x110 fs/buffer.c:2771 req_bio_endio block/blk-mq.c:783 [inline] blk_update_request+0x53f/0x1020 block/blk-mq.c:928 blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1051 blk_complete_reqs block/blk-mq.c:1131 [inline] blk_done_softirq+0x103/0x150 block/blk-mq.c:1136 __do_softirq+0x2ab/0x908 kernel/softirq.c:553 run_ksoftirqd+0xc5/0x120 kernel/softirq.c:921 smpboot_thread_fn+0x530/0x9f0 kernel/smpboot.c:164 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 The buggy address belongs to the virtual mapping at [ffffc90009fc8000, ffffc90009fd1000) created by: copy_process+0x5d1/0x41a0 kernel/fork.c:2327 The buggy address belongs to the physical page: page:ffffea0000a73940 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x29ce5 memcg:ffff88806cdb5a02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88806cdb5a02 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 5068, tgid 5068 (syz-executor171), ts 718574313429, free_ts 657162810996 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x1e6/0x210 mm/page_alloc.c:1536 prep_new_page mm/page_alloc.c:1543 [inline] get_page_from_freelist+0x31db/0x3360 mm/page_alloc.c:3170 __alloc_pages+0x255/0x670 mm/page_alloc.c:4426 vm_area_alloc_pages mm/vmalloc.c:3063 [inline] __vmalloc_area_node mm/vmalloc.c:3139 [inline] __vmalloc_node_range+0x9a3/0x1490 mm/vmalloc.c:3320 alloc_thread_stack_node kernel/fork.c:309 [inline] dup_task_struct+0x3e5/0x7d0 kernel/fork.c:1118 copy_process+0x5d1/0x41a0 kernel/fork.c:2327 kernel_clone+0x222/0x840 kernel/fork.c:2909 __do_sys_clone kernel/fork.c:3052 [inline] __se_sys_clone kernel/fork.c:3036 [inline] __x64_sys_clone+0x258/0x2a0 kernel/fork.c:3036 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1136 [inline] free_unref_page_prepare+0x8c3/0x9f0 mm/page_alloc.c:2312 free_unref_page+0x37/0x3f0 mm/page_alloc.c:2405 kasan_depopulate_vmalloc_pte+0x74/0x90 mm/kasan/shadow.c:427 apply_to_pte_range mm/memory.c:2586 [inline] apply_to_pmd_range mm/memory.c:2630 [inline] apply_to_pud_range mm/memory.c:2666 [inline] apply_to_p4d_range mm/memory.c:2702 [inline] __apply_to_page_range+0x8e2/0xe00 mm/memory.c:2736 kasan_release_vmalloc+0x9a/0xb0 mm/kasan/shadow.c:544 __purge_vmap_area_lazy+0xc0f/0x19c0 mm/vmalloc.c:1770 drain_vmap_area_work+0x40/0xd0 mm/vmalloc.c:1804 process_one_work kernel/workqueue.c:2630 [inline] process_scheduled_works+0x90f/0x1400 kernel/workqueue.c:2703 worker_thread+0xa5f/0xff0 kernel/workqueue.c:2784 kthread+0x2d3/0x370 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 Memory state around the buggy address: ffffc90009fcf600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 ffffc90009fcf680: f2 f2 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00 >ffffc90009fcf700: 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 f2 f2 ^ ffffc90009fcf780: f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 ffffc90009fcf800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================