ci2 starts bisection 2023-03-24 04:44:37.23669058 +0000 UTC m=+40737.740484903
bisecting fixing commit since 833477fce7a14d43ae4c07f8ddc32fa5119471a2
building syzkaller on 80b58a4201a50d022574c185b387d54b3d442aae
ensuring issue is reproducible on original commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2

testing commit 833477fce7a14d43ae4c07f8ddc32fa5119471a2 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 4d5e0c6b79931ae1b413ab2ad2ba2d608fdfaa86a160687652a0bf9cbb087526
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: BUG: unable to handle kernel paging request in writeback_single_inode
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: BUG: unable to handle kernel paging request in inode_wait_for_writeback
run #13: OK
run #14: OK
run #15: OK
run #16: OK
run #17: OK
run #18: OK
run #19: OK
testing current HEAD 1e760fa3596e8c7f08412712c168288b79670d78
testing commit 1e760fa3596e8c7f08412712c168288b79670d78 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 85dbdf0a39a5066e8fa090f383b1a561651a9263d7ac5b8cffd404579b5f1d16
all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync
revisions tested: 2, total time: 52m22.909730161s (build: 28m18.346429953s, test: 21m45.707073956s)
the crash still happens on HEAD
commit msg: Merge tag 'gfs2-v6.3-rc3-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2
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 ffffc9000624f820 by task ksoftirqd/0/15

CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.3.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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+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
 </TASK>

The buggy address belongs to the virtual mapping at
 [ffffc90006248000, ffffc90006251000) created by:
 copy_process+0x3d5/0x3b60

The buggy address belongs to the physical page:
page:ffffea0001b1b300 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6c6cc
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 14535, tgid 14535 (syz-executor326), ts 468666185828, free_ts 468605612210
 get_page_from_freelist+0x31e9/0x3360
 __alloc_pages+0x255/0x670
 __vmalloc_node_range+0x700/0x1080
 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
 tlb_flush_mmu+0xe9/0x1e0
 tlb_finish_mmu+0xb6/0x1c0
 exit_mmap+0x267/0x670
 __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:
 ffffc9000624f700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc9000624f780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000624f800: f1 f1 f1 f1 00 00 00 00 00 00 00 f2 f2 f2 f2 f2
                                  ^
 ffffc9000624f880: 00 f2 f2 f2 01 f3 f3 f3 00 00 00 00 00 00 00 00
 ffffc9000624f900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
==================================================================