ci starts bisection 2022-11-08 05:20:07.53916938 +0000 UTC m=+12933.375991799 bisecting fixing commit since 4fe89d07dcc2804c8b562f6c7896a45643d34b2f building syzkaller on feb5635181eb12a6e3516172a3f5af06a3bc93e1 ensuring issue is reproducible on original commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f testing commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: e13cad1ed0b38ee93754794181480ae6cde2217e06b9447e86b2b19af7825621 run #0: crashed: WARNING: locking bug 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: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #4: crashed: invalid opcode in corrupted run #5: crashed: WARNING: locking bug in inode_wait_for_writeback run #6: crashed: BUG: unable to handle kernel paging request 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 inode_wait_for_writeback run #9: crashed: WARNING: locking bug 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 truncate_inode_pages_final run #12: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #13: crashed: WARNING: locking bug in inode_wait_for_writeback run #14: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #15: crashed: BUG: unable to handle kernel paging request in ntfs_fill_super 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: BUG: unable to handle kernel paging request in inode_wait_for_writeback 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: c7a2a71e0c5a93aa4efa5ccf51620f10eaf1864dcd5be00ac1e85e8f517079ed all runs: crashed: KASAN: stack-out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 30m0.747210785s (build: 13m58.719293914s, test: 15m22.796796277s) 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 ffffc90004a2f9c8 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 [ffffc90004a28000, ffffc90004a31000) created by: kernel_clone+0xb8/0x710 kernel/fork.c:2671 The buggy address belongs to the physical page: page:ffffea000095e680 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2579a memcg:ffff888026beac02 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff888026beac02 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 7358, tgid 7358 (syz-executor.0), ts 159749011231, free_ts 158613305347 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_list+0x172/0xc40 mm/page_alloc.c:3529 release_pages+0x2db/0x1090 mm/swap.c:1055 __pagevec_release+0x59/0xe0 mm/swap.c:1075 pagevec_release include/linux/pagevec.h:71 [inline] folio_batch_release include/linux/pagevec.h:135 [inline] truncate_inode_pages_range+0x267/0xca0 mm/truncate.c:373 kill_bdev block/bdev.c:76 [inline] blkdev_flush_mapping+0x11a/0x250 block/bdev.c:662 blkdev_put_whole+0xa0/0xd0 block/bdev.c:693 blkdev_put+0x1c7/0x660 block/bdev.c:953 blkdev_close+0x5f/0x90 block/fops.c:499 __fput+0x1fa/0x9a0 fs/file_table.c:320 task_work_run+0x12b/0x220 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x23c/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:296 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc90004a2f880: 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 ffffc90004a2f900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc90004a2f980: 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 00 00 ^ ffffc90004a2fa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc90004a2fa80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 ==================================================================