ci starts bisection 2023-02-27 13:06:19.235722972 +0000 UTC m=+20032.961280741 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: bd302602a4b45a1931a0eefa34aa32de347b9104c296c89d63f8c34dd417246e 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: 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 f3a2439f20d918930cc4ae8f76fe1c1afd26958f testing commit f3a2439f20d918930cc4ae8f76fe1c1afd26958f gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 5e61cdff5c1a6a7eff5cd06f646a50a235d4045bae85d28066ec675995a2c411 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: 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: 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: 39m43.148305084s (build: 16m1.881993944s, test: 22m51.80775451s) the crash still happens on HEAD commit msg: Merge tag 'rproc-v6.3' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/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 ffffc9000d787800 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.2.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: dump_stack_lvl+0x167/0x220 print_report+0x163/0x540 kasan_report+0x143/0x170 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+0x311/0xb1a run_ksoftirqd+0xc5/0x120 smpboot_thread_fn+0x534/0x8e0 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 The buggy address belongs to the virtual mapping at [ffffc9000d780000, ffffc9000d789000) created by: copy_process+0x3d5/0x3b10 The buggy address belongs to the physical page: page:ffffea0001cc0600 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x73018 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 22608, tgid 22608 (syz-executor546), ts 548098464792, free_ts 547994431263 get_page_from_freelist+0x37e0/0x3970 __alloc_pages+0x291/0x7f0 __vmalloc_node_range+0x700/0x1080 dup_task_struct+0x575/0x690 copy_process+0x3d5/0x3b10 kernel_clone+0x190/0x700 __x64_sys_clone+0x230/0x280 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: free_unref_page_prepare+0xf0e/0xf70 free_unref_page+0x37/0x3f0 vfree+0x11f/0x240 delayed_vfree_work+0x3c/0x70 process_one_work+0x7ee/0x1010 worker_thread+0x8c9/0xfd0 kthread+0x232/0x2b0 ret_from_fork+0x1f/0x30 Memory state around the buggy address: ffffc9000d787700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000d787780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000d787800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000d787880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000d787900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================