ci starts bisection 2023-05-26 17:09:47.516907182 +0000 UTC m=+5688.298075849 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: 55ab9fe86360a1dfd99a7c370a6a3f2a4a550ad3bedd490cb829b7baa6254e72 run #0: failed: failed to run command in VM: broken console: Permission denied (publickey) run #1: crashed: WARNING: suspicious RCU usage in ntfs_fill_super 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: WARNING: suspicious RCU usage in ntfs_fill_super run #7: crashed: WARNING in match_held_lock run #8: crashed: WARNING: locking bug 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: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #13: OK run #14: crashed: BUG: unable to handle kernel paging request in inode_wait_for_writeback run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK testing current HEAD 0d85b27b0cc6b5cf54567c5ad913a247a71583ce testing commit 0d85b27b0cc6b5cf54567c5ad913a247a71583ce gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: a4808dda56d04bd3940b3a9a5848b9f7ee6b21d3de142d1a7917d2bde3ec5a67 all runs: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 32m57.612090553s (build: 13m4.898212648s, test: 19m0.503131308s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge tag '6.4-rc3-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6 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:96 [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:329 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 Write of size 4 at addr ffffc900056af978 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.4.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/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:351 print_report mm/kasan/report.c:462 [inline] kasan_report+0x118/0x130 mm/kasan/report.c:572 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:96 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:257 [inline] put_bh include/linux/buffer_head.h:329 [inline] end_buffer_read_sync+0x5c/0x90 fs/buffer.c:161 end_bio_bh_io_sync+0xa9/0xf0 fs/buffer.c:2730 req_bio_endio block/blk-mq.c:761 [inline] blk_update_request+0x45b/0x1320 block/blk-mq.c:906 blk_mq_end_request+0x51/0x3f0 block/blk-mq.c:1023 blk_complete_reqs+0xa0/0xd0 block/blk-mq.c:1101 __do_softirq+0x1d0/0x901 kernel/softirq.c:571 run_ksoftirqd kernel/softirq.c:939 [inline] run_ksoftirqd+0x2d/0x60 kernel/softirq.c:931 smpboot_thread_fn+0x548/0x8c0 kernel/smpboot.c:164 kthread+0x2e6/0x3c0 kernel/kthread.c:379 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 The buggy address belongs to the virtual mapping at [ffffc900056a8000, ffffc900056b1000) created by: kernel_clone+0xb8/0x5f0 kernel/fork.c:2918 The buggy address belongs to the physical page: page:ffffea0000971c40 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x25c71 memcg:ffff88801a773402 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88801a773402 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 5290, tgid 5290 (syz-executor.0), ts 327760884181, free_ts 326499609352 prep_new_page mm/page_alloc.c:1738 [inline] get_page_from_freelist+0xf85/0x2ca0 mm/page_alloc.c:3502 __alloc_pages+0x1c7/0x490 mm/page_alloc.c:4768 vm_area_alloc_pages mm/vmalloc.c:3009 [inline] __vmalloc_area_node mm/vmalloc.c:3085 [inline] __vmalloc_node_range+0x7fb/0x1060 mm/vmalloc.c:3257 alloc_thread_stack_node kernel/fork.c:313 [inline] dup_task_struct kernel/fork.c:1116 [inline] copy_process+0x117a/0x6c40 kernel/fork.c:2333 kernel_clone+0xb8/0x5f0 kernel/fork.c:2918 __do_sys_clone+0xa1/0xe0 kernel/fork.c:3061 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:1302 [inline] free_unref_page_prepare+0x620/0xc80 mm/page_alloc.c:2564 free_unref_page_list+0xdf/0xa70 mm/page_alloc.c:2705 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+0x239/0x750 mm/mmap.c:3123 __mmput+0xf3/0x440 kernel/fork.c:1351 exit_mm kernel/exit.c:564 [inline] do_exit+0x885/0x2470 kernel/exit.c:858 do_group_exit+0xb0/0x250 kernel/exit.c:1021 get_signal+0x1d26/0x1f90 kernel/signal.c:2874 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+0x11f/0x240 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:297 do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc900056af880: f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900056af900: 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3 00 00 00 >ffffc900056af980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc900056afa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffc900056afa80: 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2 00 00 00 f3 ==================================================================