ci starts bisection 2023-02-24 23:29:40.626193618 +0000 UTC m=+34704.828771563 bisecting fixing commit since a5088ee7251e5106a4efa9588a73866eb4b4154e building syzkaller on eab8f94940b33c0a2cbc7d8eb2219862b6864b19 ensuring issue is reproducible on original commit a5088ee7251e5106a4efa9588a73866eb4b4154e testing commit a5088ee7251e5106a4efa9588a73866eb4b4154e gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: cdc3a36409b461ccf209802cdec1ea55cf5ebc684969a021641e550feb8bd73a run #0: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #1: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #2: crashed: WARNING: suspicious RCU usage in ntfs_fill_super run #3: crashed: WARNING: suspicious RCU usage in ntfs_fill_super run #4: crashed: KASAN: wild-memory-access Read in inode_wait_for_writeback run #5: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #6: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #7: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #8: crashed: KASAN: wild-memory-access Read in inode_wait_for_writeback run #9: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #10: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #11: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #12: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #13: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #14: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #15: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #16: crashed: KASAN: wild-memory-access Read in inode_wait_for_writeback run #17: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #18: OK run #19: OK testing current HEAD 8cbd92339db08b19b93d1637e5799ff2a8dddfd2 testing commit 8cbd92339db08b19b93d1637e5799ff2a8dddfd2 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 2b0d439b8560f287ccb707390099237682c795ac2b440afb6c3b872f53dfba77 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 30m44.791489306s (build: 13m44.320875792s, test: 16m11.008103248s) the crash still happens on HEAD commit msg: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma crash: KASAN: out-of-bounds Write in end_buffer_read_sync ================================================================== BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:102 [inline] BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:323 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 Write of size 4 at addr ffffc900031279a8 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.2.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:319 print_report mm/kasan/report.c:430 [inline] kasan_report+0x118/0x130 mm/kasan/report.c:536 check_region_inline mm/kasan/generic.c:181 [inline] kasan_check_range+0x13d/0x180 mm/kasan/generic.c:187 instrument_atomic_read_write include/linux/instrumented.h:102 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] put_bh include/linux/buffer_head.h:323 [inline] end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2703 req_bio_endio block/blk-mq.c:795 [inline] blk_update_request+0x31f/0x1320 block/blk-mq.c:927 blk_mq_end_request+0x46/0x70 block/blk-mq.c:1054 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1132 __do_softirq+0x2df/0xadf kernel/softirq.c:571 run_ksoftirqd kernel/softirq.c:934 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926 smpboot_thread_fn+0x548/0x8f0 kernel/smpboot.c:164 kthread+0x294/0x330 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 The buggy address belongs to the virtual mapping at [ffffc90003120000, ffffc90003129000) created by: kernel_clone+0xb8/0x720 kernel/fork.c:2684 The buggy address belongs to the physical page: page:ffffea0000698dc0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1a637 memcg:ffff8880756bf782 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff8880756bf782 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 9683, tgid 9683 (syz-executor.0), ts 183915646259, free_ts 179259907321 prep_new_page mm/page_alloc.c:2552 [inline] get_page_from_freelist+0x1190/0x2f80 mm/page_alloc.c:4325 __alloc_pages+0x1c7/0x5b0 mm/page_alloc.c:5591 vm_area_alloc_pages mm/vmalloc.c:2943 [inline] __vmalloc_area_node mm/vmalloc.c:3011 [inline] __vmalloc_node_range+0x7c8/0xf50 mm/vmalloc.c:3181 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:984 [inline] copy_process+0x10db/0x6c40 kernel/fork.c:2100 kernel_clone+0xb8/0x720 kernel/fork.c:2684 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2825 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 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:1453 [inline] free_pcp_prepare+0x65a/0xb40 mm/page_alloc.c:1503 free_unref_page_prepare mm/page_alloc.c:3387 [inline] free_unref_page+0x19/0x480 mm/page_alloc.c:3482 kasan_depopulate_vmalloc_pte+0x5c/0x70 mm/kasan/shadow.c:413 apply_to_pte_range mm/memory.c:2578 [inline] apply_to_pmd_range mm/memory.c:2622 [inline] apply_to_pud_range mm/memory.c:2658 [inline] apply_to_p4d_range mm/memory.c:2694 [inline] __apply_to_page_range+0x4fe/0xbc0 mm/memory.c:2728 kasan_release_vmalloc+0xa7/0xc0 mm/kasan/shadow.c:530 __purge_vmap_area_lazy+0x6ed/0x2500 mm/vmalloc.c:1767 drain_vmap_area_work+0x49/0xb0 mm/vmalloc.c:1800 process_one_work+0x8ba/0x1590 kernel/workqueue.c:2390 worker_thread+0x598/0xec0 kernel/workqueue.c:2537 kthread+0x294/0x330 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 Memory state around the buggy address: ffffc90003127880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90003127900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90003127980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc90003127a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90003127a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================