ci2 starts bisection 2022-11-04 15:14:10.747232738 +0000 UTC m=+66192.103660667 bisecting fixing commit since 521a547ced6477c54b4b0cc206000406c221b4d6 building syzkaller on dd9a85ff356d74a765888403f1b70faece9e642b ensuring issue is reproducible on original commit 521a547ced6477c54b4b0cc206000406c221b4d6 testing commit 521a547ced6477c54b4b0cc206000406c221b4d6 gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: ffd5b9686b63c34ea9dd8f7d14e6c1dcae43b0ca80023662670009fa8819f8ca run #0: crashed: INFO: rcu detected stall in corrupted run #1: crashed: INFO: rcu detected stall in corrupted run #2: crashed: INFO: rcu detected stall in corrupted run #3: crashed: INFO: rcu detected stall in corrupted run #4: crashed: INFO: rcu detected stall in corrupted run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: INFO: rcu detected stall in corrupted run #7: crashed: INFO: rcu detected stall in corrupted run #8: crashed: WARNING: nested lock was not taken in ntfs_fill_super run #9: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #10: crashed: BUG: scheduling while atomic in exit_to_user_mode_loop run #11: crashed: BUG: unable to handle kernel paging request in evict run #12: crashed: BUG: unable to handle kernel paging request in ntfs_fill_super run #13: OK run #14: OK run #15: OK run #16: OK run #17: OK run #18: OK run #19: OK testing current HEAD ee6050c8af96bba2f81e8b0793a1fc2f998fcd20 testing commit ee6050c8af96bba2f81e8b0793a1fc2f998fcd20 gcc compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 72c0f90af6ec30d5e1a7ecba7dcfefa18cef0b560889b725269359ed02b80bab run #0: crashed: INFO: rcu detected stall in corrupted run #1: crashed: INFO: rcu detected stall in corrupted run #2: crashed: INFO: rcu detected stall in corrupted run #3: crashed: INFO: rcu detected stall in corrupted run #4: crashed: INFO: rcu detected stall in corrupted run #5: crashed: INFO: rcu detected stall in corrupted run #6: crashed: INFO: rcu detected stall in corrupted run #7: crashed: INFO: rcu detected stall in corrupted run #8: crashed: KASAN: out-of-bounds Write in end_buffer_read_sync run #9: OK revisions tested: 2, total time: 49m7.842719258s (build: 25m36.137785455s, test: 22m54.441645814s) the crash still happens on HEAD commit msg: Merge tag 'ata-6.1-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata 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:320 [inline] BUG: KASAN: out-of-bounds in end_buffer_read_sync+0x85/0x90 fs/buffer.c:160 Write of size 4 at addr ffffc90002f07860 by task ksoftirqd/1/21 CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 6.1.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x12a/0x1be lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 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+0x85/0x90 fs/buffer.c:160 end_bio_bh_io_sync+0x87/0xd0 fs/buffer.c:2655 req_bio_endio block/blk-mq.c:762 [inline] blk_update_request+0x3c4/0x1040 block/blk-mq.c:894 blk_mq_end_request+0x34/0x60 block/blk-mq.c:1021 blk_complete_reqs block/blk-mq.c:1099 [inline] blk_done_softirq+0x95/0x140 block/blk-mq.c:1104 __do_softirq+0x277/0x738 kernel/softirq.c:571 run_ksoftirqd+0xa2/0x100 kernel/softirq.c:934 smpboot_thread_fn+0x523/0x8c0 kernel/smpboot.c:164 kthread+0x228/0x2a0 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 [ffffc90002f00000, ffffc90002f09000) created by: dup_task_struct+0x55/0x440 kernel/fork.c:974 The buggy address belongs to the physical page: page:ffffea0000992640 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x26499 memcg:ffff88802537e582 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88802537e582 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 7566, tgid 7566 (syz-executor.2), ts 142955403713, free_ts 142830527598 prep_new_page mm/page_alloc.c:2539 [inline] get_page_from_freelist+0x742/0x7c0 mm/page_alloc.c:4288 __alloc_pages+0x259/0x560 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+0x66f/0xfb0 mm/vmalloc.c:3213 alloc_thread_stack_node+0x27f/0x410 kernel/fork.c:311 dup_task_struct+0x55/0x440 kernel/fork.c:974 copy_process+0x401/0x3b90 kernel/fork.c:2084 kernel_clone+0x15d/0x490 kernel/fork.c:2671 __do_sys_clone kernel/fork.c:2812 [inline] __se_sys_clone kernel/fork.c:2796 [inline] __x64_sys_clone+0x223/0x280 kernel/fork.c:2796 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/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+0x80c/0x8f0 mm/page_alloc.c:1509 free_unref_page_prepare mm/page_alloc.c:3387 [inline] free_unref_page_list+0xb4/0x7b0 mm/page_alloc.c:3529 release_pages+0x1991/0x1b30 mm/swap.c:1055 __pagevec_release+0x5f/0xd0 mm/swap.c:1075 pagevec_release include/linux/pagevec.h:71 [inline] folio_batch_release include/linux/pagevec.h:135 [inline] invalidate_mapping_pagevec+0x54b/0x620 mm/truncate.c:543 ntfs_loadlog_and_replay+0x32d/0x540 fs/ntfs3/fsntfs.c:305 ntfs_fill_super+0x1e21/0x3c30 fs/ntfs3/super.c:1018 get_tree_bdev+0x3d5/0x620 fs/super.c:1324 vfs_get_tree+0x7b/0x220 fs/super.c:1531 do_new_mount+0x1df/0x930 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x20f/0x2a0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffffc90002f07700: 00 00 00 00 00 00 00 00 00 00 00 00 00 f2 f2 f2 ffffc90002f07780: f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 >ffffc90002f07800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffc90002f07880: 00 00 00 f2 f2 f2 f2 f2 f2 f2 f2 f2 00 00 00 00 ffffc90002f07900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================