ci starts bisection 2023-04-26 14:52:11.945215355 +0000 UTC m=+6675.619475226
bisecting fixing commit since 46452d3786a82bd732ba73fb308ae5cbe4e1e591
building syzkaller on 75c78242e3cb60e13282fa7040f13832f573320e
ensuring issue is reproducible on original commit 46452d3786a82bd732ba73fb308ae5cbe4e1e591

testing commit 46452d3786a82bd732ba73fb308ae5cbe4e1e591 gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 8c16a3ad1fcc9b12c000a54968337aeacc8ce6d0d785822e0c555ea5146f3cea
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: BUG: unable to handle kernel paging request in inode_wait_for_writeback
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 0cfd8703e7da687924371e9bc77a025bdeba9637
testing commit 0cfd8703e7da687924371e9bc77a025bdeba9637 gcc
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 171f0bdbe5ef6e814e4cc9a0b232f008d1c410bb0c113141385c0a3fdbd86bbd
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: stack-out-of-bounds Write in end_buffer_read_sync
run #2: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #3: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #4: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
run #5: crashed: KASAN: stack-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: stack-out-of-bounds Write in end_buffer_read_sync
run #9: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync
revisions tested: 2, total time: 30m30.720140457s (build: 13m11.695460147s, test: 16m40.02100923s)
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: stack-out-of-bounds Write in end_buffer_read_sync
==================================================================
BUG: KASAN: stack-out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
BUG: KASAN: stack-out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline]
BUG: KASAN: stack-out-of-bounds in put_bh include/linux/buffer_head.h:323 [inline]
BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161
Write of size 4 at addr ffffc90004c379a8 by task ksoftirqd/1/20

CPU: 1 PID: 20 Comm: ksoftirqd/1 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 lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106
 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:319
 print_report mm/kasan/report.c:430 [inline]
 kasan_report+0x118/0x130 mm/kasan/report.c:536
 check_region_inline mm/kasan/generic.c:181 [inline]
 kasan_check_range+0x13d/0x180 mm/kasan/generic.c:187
 instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
 atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline]
 put_bh include/linux/buffer_head.h:323 [inline]
 end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161
 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2700
 req_bio_endio block/blk-mq.c:795 [inline]
 blk_update_request+0x2ee/0x1180 block/blk-mq.c:927
 blk_mq_end_request+0x46/0x70 block/blk-mq.c:1054
 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1132
 __do_softirq+0x1d0/0x901 kernel/softirq.c:571
 run_ksoftirqd kernel/softirq.c:939 [inline]
 run_ksoftirqd+0x2d/0x60 kernel/softirq.c:931
 smpboot_thread_fn+0x548/0x8c0 kernel/smpboot.c:164
 kthread+0x2e6/0x3c0 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

The buggy address belongs to the virtual mapping at
 [ffffc90004c30000, ffffc90004c39000) created by:
 kernel_clone+0xb8/0x5f0 kernel/fork.c:2774

The buggy address belongs to the physical page:
page:ffffea0000aa63c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2a98f
memcg:ffff88801e99aa82
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88801e99aa82
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 10437, tgid 10437 (syz-executor.3), ts 175714219586, free_ts 175628880732
 prep_new_page mm/page_alloc.c:2553 [inline]
 get_page_from_freelist+0x1190/0x2e20 mm/page_alloc.c:4326
 __alloc_pages+0x1c7/0x490 mm/page_alloc.c:5592
 vm_area_alloc_pages mm/vmalloc.c:2957 [inline]
 __vmalloc_area_node mm/vmalloc.c:3033 [inline]
 __vmalloc_node_range+0x7fb/0x1060 mm/vmalloc.c:3205
 alloc_thread_stack_node kernel/fork.c:311 [inline]
 dup_task_struct kernel/fork.c:982 [inline]
 copy_process+0x1110/0x6ba0 kernel/fork.c:2190
 kernel_clone+0xb8/0x5f0 kernel/fork.c:2774
 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2917
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1454 [inline]
 free_pcp_prepare+0x5c7/0xa30 mm/page_alloc.c:1504
 free_unref_page_prepare mm/page_alloc.c:3388 [inline]
 free_unref_page+0x19/0x480 mm/page_alloc.c:3483
 vfree+0x120/0x730 mm/vmalloc.c:2746
 delayed_vfree_work+0x46/0x70 mm/vmalloc.c:2667
 process_one_work+0x865/0x13f0 kernel/workqueue.c:2390
 worker_thread+0x598/0xec0 kernel/workqueue.c:2537
 kthread+0x2e6/0x3c0 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

Memory state around the buggy address:
 ffffc90004c37880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90004c37900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1
>ffffc90004c37980: f1 f1 f1 f1 01 f2 00 f2 f2 f2 00 00 00 00 00 00
                                  ^
 ffffc90004c37a00: 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00
 ffffc90004c37a80: 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 00 00 00 00 00
==================================================================