ci starts bisection 2023-04-26 04:26:16.506311167 +0000 UTC m=+12707.768118803 bisecting fixing commit since e8bc52cb8df80c31c73c726ab58ea9746e9ff734 building syzkaller on aea5da898f473385f3b66c94f8aa49ca9a1c9744 ensuring issue is reproducible on original commit e8bc52cb8df80c31c73c726ab58ea9746e9ff734 testing commit e8bc52cb8df80c31c73c726ab58ea9746e9ff734 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: ec5baff946f45f8248a259e4582d43bdac0d49503a932d81531ea83c4443426b run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe 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: 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 0cfd8703e7da687924371e9bc77a025bdeba9637 testing commit 0cfd8703e7da687924371e9bc77a025bdeba9637 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 8ba1344d9622c7bed5eaf8ba5d52fccae77a804c0b686df95394c5f558116423 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #2: crashed: KASAN: stack-out-of-bounds Write in ntfs_fill_super 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: stack-out-of-bounds Write in ntfs_fill_super 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: 43m44.078177509s (build: 16m17.440224389s, test: 26m48.174672286s) the crash still happens on HEAD commit msg: Merge tag 'pm-6.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm 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 ffffc90004ebf800 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.3.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Call Trace: dump_stack_lvl+0x167/0x220 print_report+0x163/0x540 kasan_report+0x176/0x1b0 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/0x908 run_ksoftirqd+0xc5/0x120 smpboot_thread_fn+0x534/0x890 kthread+0x276/0x2f0 ret_from_fork+0x1f/0x30 The buggy address belongs to the virtual mapping at [ffffc90004eb8000, ffffc90004ec1000) created by: copy_process+0x40a/0x3c40 The buggy address belongs to the physical page: page:ffffea0001b28a00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6ca28 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 24700, tgid 24700 (syz-executor201), ts 527584154495, free_ts 527419568866 get_page_from_freelist+0x3246/0x33c0 __alloc_pages+0x255/0x670 __vmalloc_node_range+0x7cc/0x10d0 dup_task_struct+0x575/0x690 copy_process+0x40a/0x3c40 kernel_clone+0x19a/0x5f0 __x64_sys_clone+0x253/0x2a0 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+0x1a0f/0x1bc0 tlb_flush_mmu+0xe9/0x1e0 tlb_finish_mmu+0xb6/0x1c0 exit_mmap+0x358/0x7d0 __mmput+0xcb/0x300 exit_mm+0x1de/0x290 do_exit+0x4f2/0x1d10 do_group_exit+0x1b9/0x280 get_signal+0x1233/0x12e0 arch_do_signal_or_restart+0x91/0x670 exit_to_user_mode_loop+0x6a/0x100 exit_to_user_mode_prepare+0xb1/0x140 syscall_exit_to_user_mode+0x64/0x280 do_syscall_64+0x4d/0xc0 Memory state around the buggy address: ffffc90004ebf700: 00 00 00 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 f3 f3 ffffc90004ebf780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90004ebf800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc90004ebf880: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00 ffffc90004ebf900: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================