ci2 starts bisection 2023-06-01 06:56:50.776792779 +0000 UTC m=+40236.892917394 bisecting fixing commit since 3db61221f4e8f18d1dd6e45dbe9e3702ff2d67ab building syzkaller on 0042f2b4c00ce1ceeaa44a0147909fe3a6f86c5c ensuring issue is reproducible on original commit 3db61221f4e8f18d1dd6e45dbe9e3702ff2d67ab testing commit 3db61221f4e8f18d1dd6e45dbe9e3702ff2d67ab gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: fb3c7c035282e0b97fe7e13f0b7f912c964b599db5a81820c05c0697f4245f44 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM run #1: crashed: WARNING: locking bug in writeback_single_inode run #2: crashed: WARNING: locking bug in writeback_single_inode run #3: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #4: crashed: WARNING: locking bug in writeback_single_inode run #5: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #6: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #7: OK run #8: OK 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 929ed21dfdb6ee94391db51c9eedb63314ef6847 testing commit 929ed21dfdb6ee94391db51c9eedb63314ef6847 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: efae620fd73e6bbc1522b69b6d4a61b9fc19a06e60fd82b532494d6e9d260d70 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe 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 run #10: crashed: KASAN: stack-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: OK run #17: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #18: OK run #19: OK crash still not fixed/happens on the oldest tested release Reproducer flagged being flaky revisions tested: 2, total time: 59m32.128671887s (build: 33m21.569784902s, test: 25m5.343597562s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge tag '6.4-rc4-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6 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 ffffc900049c7820 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.4.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/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+0x3fb/0x1080 blk_mq_end_request+0x48/0x260 blk_done_softirq+0x83/0x120 __do_softirq+0x2ab/0x8ea run_ksoftirqd+0xa6/0x100 smpboot_thread_fn+0x534/0x890 kthread+0x276/0x2f0 ret_from_fork+0x1f/0x30 The buggy address belongs to the virtual mapping at [ffffc900049c0000, ffffc900049c9000) created by: copy_process+0x40a/0x3c80 The buggy address belongs to the physical page: page:ffffea00009a98c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x26a63 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() 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 16595, tgid 16595 (syz-executor174), ts 569337921197, free_ts 569161522211 get_page_from_freelist+0x31bf/0x3340 __alloc_pages+0x255/0x670 __vmalloc_node_range+0x7cc/0x10d0 dup_task_struct+0x5c3/0x720 copy_process+0x40a/0x3c80 kernel_clone+0x17d/0x5d0 __x64_sys_clone+0x268/0x2e0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: free_unref_page_prepare+0x8fe/0xa10 free_unref_page_list+0x596/0x830 release_pages+0x1a07/0x1bc0 __pagevec_release+0x66/0xe0 truncate_inode_pages_range+0x35e/0xd60 blkdev_flush_mapping+0x101/0x1f0 blkdev_put+0x3ce/0x5b0 blkdev_close+0x55/0x80 __fput+0x33f/0x720 task_work_run+0x20a/0x290 exit_to_user_mode_loop+0xd1/0xf0 exit_to_user_mode_prepare+0xb1/0x140 syscall_exit_to_user_mode+0x54/0x270 do_syscall_64+0x4d/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc900049c7700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900049c7780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900049c7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc900049c7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900049c7900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================