ci starts bisection 2023-02-25 01:43:14.757899935 +0000 UTC m=+42718.960477832 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: f3f3093db8fb84eddfb48f8f2a4ac200270aca347f4fa8a107db347376192880 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 ntfs_fill_super run #3: crashed: WARNING: locking bug 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: 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 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: WARNING: suspicious RCU usage in ntfs_fill_super run #12: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #13: crashed: WARNING: suspicious RCU usage in ntfs_fill_super run #14: crashed: invalid opcode in corrupted 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: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #19: OK testing current HEAD 595fa4e313fee3c0b69c10bbed6fffb803237306 testing commit 595fa4e313fee3c0b69c10bbed6fffb803237306 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 244f03d725f335c69b255256ff41dde55f9656661ef184c1d7ad8e5c5696a617 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync revisions tested: 2, total time: 53m3.730260365s (build: 19m50.037848406s, test: 32m17.079644659s) the crash still happens on HEAD commit msg: Merge tag 'soundwire-6.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire 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 ffffc9000b5a79a8 by task ksoftirqd/0/15 CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.2.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/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+0x31f/0x1320 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+0x2df/0xadf 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:308 The buggy address belongs to the virtual mapping at [ffffc9000b5a0000, ffffc9000b5a9000) created by: kernel_clone+0xb8/0x720 kernel/fork.c:2684 The buggy address belongs to the physical page: page:ffffea00006e2f00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1b8bc 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 14453, tgid 14453 (syz-executor.0), ts 311532112524, free_ts 311396266173 prep_new_page mm/page_alloc.c:2552 [inline] get_page_from_freelist+0x1190/0x2f80 mm/page_alloc.c:4325 __alloc_pages+0x1c7/0x5b0 mm/page_alloc.c:5591 vm_area_alloc_pages mm/vmalloc.c:2943 [inline] __vmalloc_area_node mm/vmalloc.c:3011 [inline] __vmalloc_node_range+0x7c8/0xf50 mm/vmalloc.c:3181 alloc_thread_stack_node kernel/fork.c:311 [inline] dup_task_struct kernel/fork.c:984 [inline] copy_process+0x10db/0x6c40 kernel/fork.c:2100 kernel_clone+0xb8/0x720 kernel/fork.c:2684 __do_sys_clone+0xa1/0xe0 kernel/fork.c:2825 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:1453 [inline] free_pcp_prepare+0x65a/0xb40 mm/page_alloc.c:1503 free_unref_page_prepare mm/page_alloc.c:3387 [inline] free_unref_page_list+0x172/0xcd0 mm/page_alloc.c:3528 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/0x620 mm/mmap.c:3047 __mmput+0xf3/0x440 kernel/fork.c:1209 exit_mm kernel/exit.c:563 [inline] do_exit+0x885/0x2500 kernel/exit.c:856 do_group_exit+0xb0/0x250 kernel/exit.c:1019 get_signal+0x1d26/0x1f90 kernel/signal.c:2859 arch_do_signal_or_restart+0x75/0x5b0 arch/x86/kernel/signal.c:306 exit_to_user_mode_loop kernel/entry/common.c:168 [inline] exit_to_user_mode_prepare+0x15f/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: ffffc9000b5a7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000b5a7900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc9000b5a7980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc9000b5a7a00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc9000b5a7a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================