ci2 starts bisection 2022-11-04 11:49:12.219440943 +0000 UTC m=+53893.575868841 bisecting fixing commit since ffb4d94b4314655cea60ab7962756e6bab72fc7e building syzkaller on feb5635181eb12a6e3516172a3f5af06a3bc93e1 ensuring issue is reproducible on original commit ffb4d94b4314655cea60ab7962756e6bab72fc7e testing commit ffb4d94b4314655cea60ab7962756e6bab72fc7e 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: 8887d3ba155cc02d9f73d123c197cf235fd4d0661c0425024963448110ac294c all runs: crashed: possible deadlock in mi_read 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: 19f9363bd1e198f74a8484dca21b7f87a58d1e448e597811da5bdaa80b8add5b all runs: crashed: possible deadlock in mi_read revisions tested: 2, total time: 35m28.564873343s (build: 28m3.376134996s, test: 6m35.555514664s) 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: possible deadlock in mi_read loop0: detected capacity change from 0 to 4096 ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512) ============================================ WARNING: possible recursive locking detected 6.1.0-rc3-syzkaller #0 Not tainted -------------------------------------------- syz-executor.0/4155 is trying to acquire lock: ffff8880727b8100 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline] ffff8880727b8100 (&ni->ni_lock/4){+.+.}-{3:3}, at: mi_read+0x1c7/0x400 fs/ntfs3/record.c:148 but task is already holding lock: ffff8880727bbc00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline] ffff8880727bbc00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xef/0x190 fs/ntfs3/namei.c:82 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&ni->ni_lock/4); lock(&ni->ni_lock/4); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by syz-executor.0/4155: #0: ffff8880727bbea0 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:766 [inline] #0: ffff8880727bbea0 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow+0x40/0x70 fs/namei.c:1701 #1: ffff8880727bbc00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline] #1: ffff8880727bbc00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xef/0x190 fs/ntfs3/namei.c:82 stack backtrace: CPU: 0 PID: 4155 Comm: syz-executor.0 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_deadlock_bug kernel/locking/lockdep.c:2990 [inline] check_deadlock kernel/locking/lockdep.c:3033 [inline] validate_chain+0x4843/0x6ae0 kernel/locking/lockdep.c:3818 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline] mi_read+0x1c7/0x400 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:69 [inline] ntfs_iget5+0x4dc/0x2fc0 fs/ntfs3/inode.c:501 dir_search_u+0x1c1/0x280 fs/ntfs3/dir.c:264 ntfs_lookup+0xfd/0x190 fs/ntfs3/namei.c:83 __lookup_slow+0x212/0x2f0 fs/namei.c:1685 lookup_slow+0x4e/0x70 fs/namei.c:1702 walk_component+0x27c/0x3a0 fs/namei.c:1993 lookup_last fs/namei.c:2450 [inline] path_lookupat+0xa4/0x360 fs/namei.c:2474 filename_lookup+0x26d/0x5c0 fs/namei.c:2503 user_path_at_empty+0x33/0x150 fs/namei.c:2876 user_path_at include/linux/namei.h:57 [inline] __do_sys_open_tree fs/namespace.c:2537 [inline] __se_sys_open_tree+0x1a0/0x7c0 fs/namespace.c:2504 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 RIP: 0033:0x7f41ec88a5a9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f41ed9c2168 EFLAGS: 00000246 ORIG_RAX: 00000000000001ac RAX: ffffffffffffffda RBX: 00007f41ec9abf80 RCX: 00007f41ec88a5a9 RDX: 0000000000000800 RSI: 0000000020000140 RDI: 0000000000000003 RBP: 00007f41ec8e5580 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffce7391fcf R14: 00007f41ed9c2300 R15: 0000000000022000