ci2 starts bisection 2023-04-28 13:14:11.025345745 +0000 UTC m=+34569.732664124
bisecting fixing commit since 0326074ff4652329f2a1a9c8685104576bd8d131
building syzkaller on 267e3bb1576b2f9fa97ae49305aaaa80768ba385
ensuring issue is reproducible on original commit 0326074ff4652329f2a1a9c8685104576bd8d131

testing commit 0326074ff4652329f2a1a9c8685104576bd8d131 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 98fbe0a495c3e33967347bda9b40b117f79956065e319bc6b90417b6e2531c46
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: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #8: crashed: INFO: rcu detected stall in corrupted
run #9: crashed: INFO: rcu detected stall in corrupted
run #10: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #11: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #12: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #13: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #14: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #15: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #16: OK
run #17: OK
run #18: OK
run #19: OK
testing current HEAD 33afd4b76393627477e878b3b195d606e585d816
testing commit 33afd4b76393627477e878b3b195d606e585d816 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 3b5d933503d66fefddb4954a9cee0df11e7cf566f11d7e110040965a27b41d0e
all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync
revisions tested: 2, total time: 1h0m7.735091108s (build: 33m58.575425953s, test: 25m9.895311864s)
the crash still happens on HEAD
commit msg: Merge tag 'mm-nonmm-stable-2023-04-27-16-01' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
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 ffffc90006407820 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:
 <TASK>
 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
 </TASK>

The buggy address belongs to the virtual mapping at
 [ffffc90006400000, ffffc90006409000) created by:
 copy_process+0x40a/0x3c80

The buggy address belongs to the physical page:
page:ffffea00005e4780 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1791e
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 16800, tgid 16800 (syz-executor152), ts 614800552708, free_ts 612324066307
 get_page_from_freelist+0x31bf/0x3340
 __alloc_pages+0x255/0x670
 __vmalloc_node_range+0x7cc/0x10d0
 dup_task_struct+0x575/0x690
 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
 tlb_flush_mmu+0xe9/0x1e0
 tlb_finish_mmu+0xb6/0x1c0
 exit_mmap+0x317/0x860
 __mmput+0xcb/0x300
 exit_mm+0x1c4/0x280
 do_exit+0x4d0/0x1cf0
 do_group_exit+0x1b9/0x280
 __x64_sys_exit_group+0x3f/0x40
 do_syscall_64+0x41/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
 ffffc90006407700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90006407780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90006407800: f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f2 f2 f2 f2
                                  ^
 ffffc90006407880: 00 f2 f2 f2 01 f3 f3 f3 00 00 00 00 00 00 00 00
 ffffc90006407900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
==================================================================