ci2 starts bisection 2023-01-21 11:31:42.263298486 +0000 UTC m=+39269.111938938 bisecting fixing commit since 521a547ced6477c54b4b0cc206000406c221b4d6 building syzkaller on dd9a85ff356d74a765888403f1b70faece9e642b ensuring issue is reproducible on original commit 521a547ced6477c54b4b0cc206000406c221b4d6 testing commit 521a547ced6477c54b4b0cc206000406c221b4d6 gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 8c9e8cb37c1489310b6479a550932412052180fbf05ed2027939d48aa53f2471 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe 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: BUG: unable to handle kernel paging request in evict run #11: crashed: WARNING: lock held when returning to user space in alloc_super run #12: crashed: BUG: looking up invalid subclass: ADDR run #13: crashed: BUG: looking up invalid subclass: ADDR run #14: OK run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK testing current HEAD f883675bf6522b52cd75dc3de791680375961769 testing commit f883675bf6522b52cd75dc3de791680375961769 gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 5e921ae3eeb027a32ed492d0927fd418c97510b96aa0586ee4d15a2ba5e1f55e run #0: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #1: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync 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: 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 revisions tested: 2, total time: 49m9.930950124s (build: 31m44.321253012s, test: 15m36.433508333s) the crash still happens on HEAD commit msg: Merge tag 'gpio-fixes-for-v6.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux crash: KASAN: out-of-bounds Write in end_buffer_read_sync ================================================================== BUG: KASAN: out-of-bounds in instrument_atomic_read_write include/linux/instrumented.h:102 [inline] BUG: KASAN: out-of-bounds in atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] BUG: KASAN: out-of-bounds in put_bh include/linux/buffer_head.h:320 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x85/0x90 fs/buffer.c:160 Write of size 4 at addr ffffc90003bff820 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.2.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x12a/0x1c0 lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:306 print_report+0x107/0x1f0 mm/kasan/report.c:417 kasan_report+0xcd/0x100 mm/kasan/report.c:517 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:102 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] put_bh include/linux/buffer_head.h:320 [inline] end_buffer_read_sync+0x85/0x90 fs/buffer.c:160 end_bio_bh_io_sync+0x87/0xd0 fs/buffer.c:2655 req_bio_endio block/blk-mq.c:794 [inline] blk_update_request+0x3c4/0x1040 block/blk-mq.c:926 blk_mq_end_request+0x34/0x60 block/blk-mq.c:1053 blk_complete_reqs block/blk-mq.c:1131 [inline] blk_done_softirq+0x95/0x140 block/blk-mq.c:1136 __do_softirq+0x277/0x738 kernel/softirq.c:571 run_ksoftirqd+0xa2/0x100 kernel/softirq.c:934 smpboot_thread_fn+0x523/0x8c0 kernel/smpboot.c:164 kthread+0x228/0x2a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 The buggy address belongs to the virtual mapping at [ffffc90003bf8000, ffffc90003c01000) created by: dup_task_struct+0x55/0x440 kernel/fork.c:987 The buggy address belongs to the physical page: page:ffffea0001ca3fc0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x728ff memcg:ffff88814665dc02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88814665dc02 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 8105, tgid 8105 (syz-executor.4), ts 128978650635, free_ts 122890831355 prep_new_page mm/page_alloc.c:2531 [inline] get_page_from_freelist+0x742/0x7c0 mm/page_alloc.c:4283 __alloc_pages+0x259/0x560 mm/page_alloc.c:5549 vm_area_alloc_pages mm/vmalloc.c:2989 [inline] __vmalloc_area_node mm/vmalloc.c:3057 [inline] __vmalloc_node_range+0x72c/0x10e0 mm/vmalloc.c:3227 alloc_thread_stack_node+0x27f/0x410 kernel/fork.c:311 dup_task_struct+0x55/0x440 kernel/fork.c:987 copy_process+0x3a4/0x3a70 kernel/fork.c:2097 kernel_clone+0x15d/0x4a0 kernel/fork.c:2681 __do_sys_clone kernel/fork.c:2822 [inline] __se_sys_clone kernel/fork.c:2806 [inline] __x64_sys_clone+0x223/0x280 kernel/fork.c:2806 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/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:1446 [inline] free_pcp_prepare+0x751/0x780 mm/page_alloc.c:1496 free_unref_page_prepare mm/page_alloc.c:3369 [inline] free_unref_page+0x19/0x4c0 mm/page_alloc.c:3464 kasan_depopulate_vmalloc_pte+0x66/0x80 mm/kasan/shadow.c:372 apply_to_pte_range mm/memory.c:2600 [inline] apply_to_pmd_range mm/memory.c:2644 [inline] apply_to_pud_range mm/memory.c:2680 [inline] apply_to_p4d_range mm/memory.c:2716 [inline] __apply_to_page_range+0x6ef/0x880 mm/memory.c:2750 kasan_release_vmalloc+0x96/0xb0 mm/kasan/shadow.c:486 __purge_vmap_area_lazy+0x13fd/0x1590 mm/vmalloc.c:1776 drain_vmap_area_work+0x3c/0xd0 mm/vmalloc.c:1809 process_one_work+0x7b9/0xc60 kernel/workqueue.c:2289 worker_thread+0x8ff/0xfe0 kernel/workqueue.c:2436 kthread+0x228/0x2a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 Memory state around the buggy address: ffffc90003bff700: 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 f2 f2 ffffc90003bff780: f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 >ffffc90003bff800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc90003bff880: 00 00 00 f2 f2 f2 f2 f2 f2 f2 f2 f2 00 00 00 00 ffffc90003bff900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================