ci starts bisection 2023-03-27 12:24:41.97392236 +0000 UTC m=+12694.375878624 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: 18838b23f8cacc42774a26f8d0d6bd37ba0124a553104b662439f2c73cd4d5cc 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: 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: 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: 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: WARNING: suspicious RCU usage in ntfs_fill_super run #13: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #14: crashed: BUG: unable to handle kernel paging request in truncate_inode_pages_final 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: OK run #18: OK run #19: OK testing current HEAD 197b6b60ae7bc51dd0814953c562833143b292aa testing commit 197b6b60ae7bc51dd0814953c562833143b292aa gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 2b1e6b20d973f6a9a03048b947e46a4a2b9e224faa9b9f519dc15f506288ae11 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 31m1.90281657s (build: 14m32.943030905s, test: 15m46.670265967s) the crash still happens on HEAD commit msg: Linux 6.3-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:323 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 Write of size 4 at addr ffffc9000575f9a8 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.3.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Call Trace: __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:102 [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:2703 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:934 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926 smpboot_thread_fn+0x548/0x8c0 kernel/smpboot.c:164 kthread+0x294/0x330 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 [ffffc90005758000, ffffc90005761000) created by: kernel_clone+0xb8/0x5f0 kernel/fork.c:2679 The buggy address belongs to the physical page: page:ffffea00006ec800 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1bb20 memcg:ffff88807e0df302 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88807e0df302 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 8921, tgid 8921 (syz-executor.0), ts 140360000067, free_ts 140345920213 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:2953 [inline] __vmalloc_area_node mm/vmalloc.c:3029 [inline] __vmalloc_node_range+0x7ed/0xfc0 mm/vmalloc.c:3199 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:979 [inline] copy_process+0x10db/0x6b40 kernel/fork.c:2095 kernel_clone+0xb8/0x5f0 kernel/fork.c:2679 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2820 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_list+0x172/0xbc0 mm/page_alloc.c:3529 release_pages+0x31c/0x10c0 mm/swap.c:1042 tlb_batch_pages_flush+0x85/0x160 mm/mmu_gather.c:97 tlb_flush_mmu_free mm/mmu_gather.c:292 [inline] tlb_flush_mmu mm/mmu_gather.c:299 [inline] tlb_finish_mmu+0x110/0x6c0 mm/mmu_gather.c:391 exit_mmap+0x1cc/0x540 mm/mmap.c:3042 __mmput+0xf3/0x440 kernel/fork.c:1204 exit_mm kernel/exit.c:563 [inline] do_exit+0x885/0x2470 kernel/exit.c:856 do_group_exit+0xb0/0x250 kernel/exit.c:1019 __do_sys_exit_group kernel/exit.c:1030 [inline] __se_sys_exit_group kernel/exit.c:1028 [inline] __x64_sys_exit_group+0x35/0x40 kernel/exit.c:1028 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 Memory state around the buggy address: ffffc9000575f880: 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 00 00 00 00 00 ffffc9000575f900: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 >ffffc9000575f980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000575fa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000575fa80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================