ci2 starts bisection 2022-11-07 07:15:16.969883599 +0000 UTC m=+296658.326311498 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 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: abf081f17f34e89283ebd797f43d0018906a039b522082f002214090689771c6 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: 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 testing current HEAD f0c4d9fc9cc9462659728d168387191387e903cc testing commit f0c4d9fc9cc9462659728d168387191387e903cc 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: 714e2c80697b28381e615677e4619e9a160b7979011c6a211feed6eb8ff3a2f3 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: 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: OK run #9: OK revisions tested: 2, total time: 53m56.403242188s (build: 27m37.179445003s, test: 25m50.254313534s) the crash still happens on HEAD commit msg: Linux 6.1-rc4 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 ffffc9000a76f860 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.1.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x12a/0x1be lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 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:762 [inline] blk_update_request+0x3c4/0x1040 block/blk-mq.c:894 blk_mq_end_request+0x34/0x60 block/blk-mq.c:1021 blk_complete_reqs block/blk-mq.c:1099 [inline] blk_done_softirq+0x95/0x140 block/blk-mq.c:1104 __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:306 The buggy address belongs to the virtual mapping at [ffffc9000a768000, ffffc9000a771000) created by: dup_task_struct+0x55/0x440 kernel/fork.c:974 The buggy address belongs to the physical page: page:ffffea0001c487c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7121f 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 15816, tgid 15816 (syz-executor307), ts 595397793571, free_ts 593816635000 prep_new_page mm/page_alloc.c:2539 [inline] get_page_from_freelist+0x742/0x7c0 mm/page_alloc.c:4288 __alloc_pages+0x259/0x560 mm/page_alloc.c:5555 vm_area_alloc_pages mm/vmalloc.c:2975 [inline] __vmalloc_area_node mm/vmalloc.c:3043 [inline] __vmalloc_node_range+0x66f/0xfb0 mm/vmalloc.c:3213 alloc_thread_stack_node+0x27f/0x410 kernel/fork.c:311 dup_task_struct+0x55/0x440 kernel/fork.c:974 copy_process+0x401/0x3b90 kernel/fork.c:2084 kernel_clone+0x15d/0x490 kernel/fork.c:2671 __do_sys_clone kernel/fork.c:2812 [inline] __se_sys_clone kernel/fork.c:2796 [inline] __x64_sys_clone+0x223/0x280 kernel/fork.c:2796 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:1459 [inline] free_pcp_prepare+0x80c/0x8f0 mm/page_alloc.c:1509 free_unref_page_prepare mm/page_alloc.c:3387 [inline] free_unref_page_list+0xb4/0x7b0 mm/page_alloc.c:3529 release_pages+0x1991/0x1b30 mm/swap.c:1055 tlb_batch_pages_flush mm/mmu_gather.c:59 [inline] tlb_flush_mmu_free mm/mmu_gather.c:256 [inline] tlb_flush_mmu+0x6a4/0x8f0 mm/mmu_gather.c:263 tlb_finish_mmu+0xad/0x1c0 mm/mmu_gather.c:363 exit_mmap+0x260/0x570 mm/mmap.c:3101 __mmput+0xca/0x300 kernel/fork.c:1185 exit_mm+0x1cd/0x280 kernel/exit.c:516 do_exit+0x537/0x1c80 kernel/exit.c:807 do_group_exit+0x1b0/0x280 kernel/exit.c:950 __do_sys_exit_group kernel/exit.c:961 [inline] __se_sys_exit_group kernel/exit.c:959 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:959 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 Memory state around the buggy address: ffffc9000a76f700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000a76f780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000a76f800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000a76f880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000a76f900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================