ci starts bisection 2022-11-07 23:26:18.070455217 +0000 UTC m=+37434.023915591 bisecting fixing commit since a5088ee7251e5106a4efa9588a73866eb4b4154e building syzkaller on eab8f94940b33c0a2cbc7d8eb2219862b6864b19 ensuring issue is reproducible on original commit a5088ee7251e5106a4efa9588a73866eb4b4154e testing commit a5088ee7251e5106a4efa9588a73866eb4b4154e gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 68b18f7153be4a27c370f05ed6c55f86a1fba85cf0958d29de31c7d2e816ab89 run #0: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #1: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #2: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #3: crashed: invalid opcode in corrupted run #4: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #5: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #6: crashed: WARNING: locking bug in inode_wait_for_writeback run #7: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #8: crashed: BUG: unable to handle kernel paging request in truncate_inode_pages_final run #9: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #10: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback 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: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #14: crashed: inconsistent lock state in inode_wait_for_writeback run #15: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #16: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #17: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #18: crashed: invalid opcode in corrupted run #19: OK testing current HEAD 59f2f4b8a757412fce372f6d0767bdb55da127a8 testing commit 59f2f4b8a757412fce372f6d0767bdb55da127a8 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 10ee8ef03053abf62f59b1ecb067bd8cd5d8177785c0fac0c9f7b775fc7ee2a2 run #0: crashed: KASAN: stack-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: 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: 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: stack-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: 31m37.499879875s (build: 14m28.863552325s, test: 16m26.229795083s) the crash still happens on HEAD commit msg: fs/userfaultfd: Fix maple tree iterator in userfaultfd_unregister() 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:102 [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:320 [inline] BUG: KASAN: stack-out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:160 Write of size 4 at addr ffffc9000a1bf9c8 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+0x57/0x7d lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0 mm/kasan/report.c:495 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x13d/0x180 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+0x5c/0x90 fs/buffer.c:160 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2655 req_bio_endio block/blk-mq.c:762 [inline] blk_update_request+0x31f/0x10b0 block/blk-mq.c:894 blk_mq_end_request+0x46/0x70 block/blk-mq.c:1021 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1099 __do_softirq+0x1f7/0xad8 kernel/softirq.c:571 run_ksoftirqd kernel/softirq.c:934 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926 smpboot_thread_fn+0x548/0x8f0 kernel/smpboot.c:164 kthread+0x294/0x330 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 [ffffc9000a1b8000, ffffc9000a1c1000) created by: kernel_clone+0xb8/0x710 kernel/fork.c:2671 The buggy address belongs to the physical page: page:ffffea0001d69a40 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x75a69 memcg:ffff88801c6b2282 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88801c6b2282 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 4005, tgid 4005 (syz-executor.0), ts 201665368403, free_ts 171275556378 prep_new_page mm/page_alloc.c:2539 [inline] get_page_from_freelist+0x10b5/0x2d50 mm/page_alloc.c:4288 __alloc_pages+0x1c7/0x5a0 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+0x6f7/0xff0 mm/vmalloc.c:3213 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:974 [inline] copy_process+0x52d/0x6850 kernel/fork.c:2084 kernel_clone+0xb8/0x710 kernel/fork.c:2671 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2812 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:1459 [inline] free_pcp_prepare+0x65c/0xd90 mm/page_alloc.c:1509 free_unref_page_prepare mm/page_alloc.c:3387 [inline] free_unref_page+0x19/0x4d0 mm/page_alloc.c:3483 kasan_depopulate_vmalloc_pte+0x5c/0x70 mm/kasan/shadow.c:372 apply_to_pte_range mm/memory.c:2640 [inline] apply_to_pmd_range mm/memory.c:2684 [inline] apply_to_pud_range mm/memory.c:2720 [inline] apply_to_p4d_range mm/memory.c:2756 [inline] __apply_to_page_range+0x4fe/0xbc0 mm/memory.c:2790 kasan_release_vmalloc+0xa7/0xc0 mm/kasan/shadow.c:486 __purge_vmap_area_lazy+0x6e1/0x2270 mm/vmalloc.c:1770 drain_vmap_area_work+0x49/0xc0 mm/vmalloc.c:1799 process_one_work+0x8ba/0x14b0 kernel/workqueue.c:2289 worker_thread+0x598/0xec0 kernel/workqueue.c:2436 kthread+0x294/0x330 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 Memory state around the buggy address: ffffc9000a1bf880: f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000a1bf900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000a1bf980: 00 00 f1 f1 f1 f1 f1 f1 01 f2 00 f2 f2 f2 00 00 ^ ffffc9000a1bfa00: 00 00 00 00 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 ffffc9000a1bfa80: 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 00 ==================================================================