ci2 starts bisection 2023-03-29 12:13:56.425184404 +0000 UTC m=+9937.438843405 bisecting fixing commit since 0326074ff4652329f2a1a9c8685104576bd8d131 building syzkaller on 267e3bb1576b2f9fa97ae49305aaaa80768ba385 ensuring issue is reproducible on original commit 0326074ff4652329f2a1a9c8685104576bd8d131 testing commit 0326074ff4652329f2a1a9c8685104576bd8d131 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: beb40aae2438e9a5bef5c7e587afa3de18a5a63a4d0ed9173ca7b273f43ef9a6 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM 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: INFO: rcu detected stall in corrupted run #8: crashed: INFO: rcu detected stall in corrupted run #9: crashed: INFO: rcu detected stall in corrupted run #10: crashed: INFO: rcu detected stall in corrupted run #11: crashed: INFO: rcu detected stall in corrupted run #12: crashed: INFO: rcu detected stall in corrupted run #13: crashed: INFO: rcu detected stall in corrupted run #14: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #15: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync run #16: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #17: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync run #18: OK run #19: OK testing current HEAD fcd476ea6a888ef6e6627f4c21a2ea8cca3e9312 testing commit fcd476ea6a888ef6e6627f4c21a2ea8cca3e9312 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 9a1a8e05edb8749e30c0fcf8070356ba54da90f4df123df63cd9c6f230da9d26 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: KASAN: out-of-bounds Write in end_buffer_read_sync 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 revisions tested: 2, total time: 59m32.78492991s (build: 34m4.108814144s, test: 23m29.447782972s) the crash still happens on HEAD commit msg: Merge tag 'urgent-rcu.2023.03.28a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu 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 ffffc90002dff820 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.3.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/17/2023 Call Trace: dump_stack_lvl+0x12e/0x1d0 print_report+0x163/0x510 kasan_report+0x108/0x140 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+0x2ab/0x8ea run_ksoftirqd+0xa6/0x100 smpboot_thread_fn+0x534/0x890 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 The buggy address belongs to the virtual mapping at [ffffc90002df8000, ffffc90002e01000) created by: copy_process+0x3d5/0x3b60 The buggy address belongs to the physical page: page:ffffea000082c780 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20b1e 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 17805, tgid 17805 (syz-executor392), ts 542103154984, free_ts 540636527703 get_page_from_freelist+0x31e9/0x3360 __alloc_pages+0x255/0x670 __vmalloc_node_range+0x7d1/0x1070 dup_task_struct+0x575/0x690 copy_process+0x3d5/0x3b60 kernel_clone+0x17d/0x5d0 __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+0xe2f/0xe70 free_unref_page+0x37/0x3f0 kasan_depopulate_vmalloc_pte+0x6a/0x80 __apply_to_page_range+0x6e4/0x830 kasan_release_vmalloc+0x9a/0xb0 __purge_vmap_area_lazy+0x1293/0x1500 drain_vmap_area_work+0x3b/0xc0 process_one_work+0x7c4/0xe70 worker_thread+0x8c9/0xfd0 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 Memory state around the buggy address: ffffc90002dff700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90002dff780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90002dff800: f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f2 f2 f2 f2 ^ ffffc90002dff880: 00 f2 f2 f2 01 f3 f3 f3 00 00 00 00 00 00 00 00 ffffc90002dff900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 ==================================================================