ci2 starts bisection 2023-04-23 07:10:18.417257677 +0000 UTC m=+164559.532085037 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: 0be98404271e34048f475b397fc8267de6ffce10b39655c1c2d6d2e83818a6ce 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: 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: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #14: crashed: WARNING: locking bug in writeback_single_inode 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: OK run #18: OK run #19: OK testing current HEAD 622322f53c6d9ddd3c2a4aad852b3e1adbd56da7 testing commit 622322f53c6d9ddd3c2a4aad852b3e1adbd56da7 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: f74eca59b1851fbd05afb859ecc1c244d2da5ffdd6ffdab9e5acafefb8f60bff run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM run #1: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM 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: 57m43.256783835s (build: 33m56.359449321s, test: 18m0.125433241s) the crash still happens on HEAD commit msg: Merge tag 'mips-fixes_6.3_2' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux 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 ffffc9000ad97820 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.3.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/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 [ffffc9000ad90000, ffffc9000ad99000) created by: copy_process+0x3d5/0x3b60 The buggy address belongs to the physical page: page:ffffea00007a9480 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1ea52 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 10744, tgid 10744 (syz-executor.0), ts 267152823400, free_ts 266882363271 get_page_from_freelist+0x31e9/0x3360 __alloc_pages+0x255/0x670 __vmalloc_node_range+0x7cc/0x10d0 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_list+0x596/0x830 release_pages+0x1a07/0x1bc0 tlb_flush_mmu+0xe9/0x1e0 tlb_finish_mmu+0xb6/0x1c0 exit_mmap+0x325/0x790 __mmput+0xcb/0x300 exit_mm+0x1c4/0x280 do_exit+0x4d0/0x1cf0 do_group_exit+0x1b9/0x280 get_signal+0x11d1/0x1280 arch_do_signal_or_restart+0x7f/0x660 exit_to_user_mode_loop+0x6a/0xf0 exit_to_user_mode_prepare+0xb1/0x140 syscall_exit_to_user_mode+0x54/0x270 do_syscall_64+0x4d/0xc0 Memory state around the buggy address: ffffc9000ad97700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000ad97780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000ad97800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000ad97880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000ad97900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================