ci2 starts bisection 2023-04-01 21:10:26.512099505 +0000 UTC m=+301327.525758497 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: 485c8b5c3f817525b92c6738ccdec45c7dd4975f5f224f26fb0d928a9a7b4af1 run #0: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync run #1: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #2: crashed: KASAN: stack-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: OK run #7: OK run #8: OK run #9: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync 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 93e2b01740863cf2f4a58887ac1384e6324b50a2 testing commit 93e2b01740863cf2f4a58887ac1384e6324b50a2 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: eb43f61a65906757082d6687325d6ba0aec09ed71100713ba9f9a4dde1bb7bb2 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 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: OK 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: OK Reproducer flagged being flaky revisions tested: 2, total time: 55m34.128211516s (build: 30m29.050965821s, test: 23m16.505549511s) the crash still happens on HEAD commit msg: Merge tag 'pinctrl-v6.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl 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 ffffc9000c8b7820 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/02/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 [ffffc9000c8b0000, ffffc9000c8b9000) created by: copy_process+0x3d5/0x3b60 The buggy address belongs to the physical page: page:ffffea0000a71540 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x29c55 memcg:ffff888026e53a02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888026e53a02 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 19310, tgid 19310 (syz-executor139), ts 563239906612, free_ts 563086006328 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_list+0x596/0x830 release_pages+0x1a07/0x1bc0 __pagevec_release+0x66/0xe0 truncate_inode_pages_range+0x360/0xd50 blkdev_flush_mapping+0xfb/0x1f0 blkdev_put+0x3da/0x5c0 deactivate_locked_super+0x75/0xd0 cleanup_mnt+0x358/0x3e0 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: ffffc9000c8b7700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000c8b7780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000c8b7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000c8b7880: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 ffffc9000c8b7900: 00 f2 f2 f2 00 00 00 f3 f3 f3 f3 f3 00 00 00 00 ==================================================================