ci starts bisection 2023-05-26 09:49:36.356833617 +0000 UTC m=+23823.538339681 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: e0147e856db936aa2f73f64e3e3d20ee4b5886a53b82e5182f61213268f5aab7 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: OK run #13: OK run #14: OK run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK testing current HEAD 0d85b27b0cc6b5cf54567c5ad913a247a71583ce testing commit 0d85b27b0cc6b5cf54567c5ad913a247a71583ce gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: c8a220079d911ceaa54dffb97fe04886d7430bf00e7dc4cc3242e02ea5042b45 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 38m52.58585843s (build: 15m51.023660967s, test: 22m9.856663853s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge tag '6.4-rc3-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 ffffc900031ef800 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.4.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/16/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+0x3fb/0x1080 blk_mq_end_request+0x48/0x260 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 [ffffc900031e8000, ffffc900031f1000) created by: copy_process+0x40a/0x3c40 The buggy address belongs to the physical page: page:ffffea00009c5cc0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x27173 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 24840, tgid 24840 (syz-executor634), ts 532792560796, free_ts 532736351979 get_page_from_freelist+0x321c/0x33a0 __alloc_pages+0x255/0x670 __vmalloc_node_range+0x7cc/0x10d0 dup_task_struct+0x5c3/0x720 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+0x8fe/0xa10 free_unref_page_list+0x596/0x830 release_pages+0x1a0f/0x1bc0 tlb_flush_mmu+0xe9/0x1e0 tlb_finish_mmu+0xb6/0x1c0 exit_mmap+0x351/0x890 __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: ffffc900031ef700: f1 f1 f1 f1 00 f3 f3 f3 00 00 00 00 00 00 00 00 ffffc900031ef780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900031ef800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc900031ef880: f1 f1 f1 f1 00 00 00 f3 f3 f3 f3 f3 00 00 00 00 ffffc900031ef900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================