ci2 starts bisection 2023-02-22 03:45:58.772280129 +0000 UTC m=+31805.426784472 bisecting fixing commit since 833477fce7a14d43ae4c07f8ddc32fa5119471a2 building syzkaller on 80b58a4201a50d022574c185b387d54b3d442aae ensuring issue is reproducible on original commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2 testing commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: d569717a112ddd8e7a3aea4ed7b7e0da6e5af8046f16eca4aa1a1e4d8aec38b4 run #0: crashed: INFO: rcu detected stall in corrupted run #1: crashed: INFO: rcu detected stall in corrupted run #2: crashed: INFO: rcu detected stall in corrupted run #3: crashed: INFO: rcu detected stall in corrupted run #4: crashed: INFO: rcu detected stall in corrupted run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: INFO: rcu detected stall in corrupted run #7: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #8: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #9: OK run #10: OK run #11: OK run #12: OK run #13: OK run #14: OK run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK reproducer seems to be flaky testing current HEAD 5b7c4cabbb65f5c469464da6c5f614cbd7f730f2 testing commit 5b7c4cabbb65f5c469464da6c5f614cbd7f730f2 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 490d9dd39e5b55aac7aeafa393831b7278d2f9924d10c33a7082b807217d408a run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM run #1: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #2: crashed: SYZFATAL: executor failed NUM times: executor NUM: failed to write control pipe: write |NUM: broken pipe run #3: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #4: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #5: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #6: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #7: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #8: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #9: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #10: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #11: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #12: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #13: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #14: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #15: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #16: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #17: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #18: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #19: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync Reproducer flagged being flaky revisions tested: 2, total time: 57m50.06593089s (build: 33m56.750163446s, test: 21m45.303197016s) the crash still happens on HEAD commit msg: Merge tag 'net-next-6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next crash: KASAN: out-of-bounds Write in end_buffer_read_sync ================================================================== BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x89/0x90 Write of size 4 at addr ffffc9000442f820 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 01/21/2023 Call Trace: dump_stack_lvl+0x12e/0x1d0 print_report+0x163/0x4c0 kasan_report+0xce/0x100 kasan_check_range+0x283/0x290 end_buffer_read_sync+0x89/0x90 end_bio_bh_io_sync+0x8d/0xe0 blk_update_request+0x3a3/0x1000 blk_mq_end_request+0x39/0x60 blk_done_softirq+0x83/0x120 __do_softirq+0x311/0xafc run_ksoftirqd+0xa6/0x100 smpboot_thread_fn+0x534/0x8e0 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 The buggy address belongs to the virtual mapping at [ffffc90004428000, ffffc90004431000) created by: copy_process+0x3d5/0x3b60 The buggy address belongs to the physical page: page:ffffea0001b4a900 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6d2a4 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) 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 13951, tgid 13951 (dhcpcd-run-hook), ts 484318006972, free_ts 474019292030 get_page_from_freelist+0x3434/0x35b0 __alloc_pages+0x291/0x7f0 __vmalloc_node_range+0x703/0x10b0 dup_task_struct+0x575/0x690 copy_process+0x3d5/0x3b60 kernel_clone+0x17d/0x700 __x64_sys_clone+0x228/0x290 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: free_unref_page_prepare+0xf3f/0x1040 free_unref_page+0x37/0x3f0 __vunmap+0x362/0x7a0 free_work+0x41/0x70 process_one_work+0x80e/0x1050 worker_thread+0x8c9/0xfd0 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 Memory state around the buggy address: ffffc9000442f700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000442f780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000442f800: f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f2 f2 f2 f2 ^ ffffc9000442f880: 00 f2 f2 f2 01 f3 f3 f3 00 00 00 00 00 00 00 00 ffffc9000442f900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 ==================================================================