syzbot


possible deadlock in mi_read (2)

Status: upstream: reported C repro on 2024/11/17 08:21
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+17f812893d5906837f33@syzkaller.appspotmail.com
First crash: 427d, last: 4d18h
Cause bisection: the cause commit could be any of (bisect log):
  309a43165077 rcu/kvfree: Use consistent krcp when growing kfree_rcu() page cache
  021a5ff84743 rcu/kvfree: Do not run a page work if a cache is disabled
  1e237994d9c9 rcu/kvfree: Invoke debug_rcu_bhead_unqueue() after checking bnode->gp_snap
  60888b77a06e rcu/kvfree: Make fill page cache start from krcp->nr_bkv_objs
  f32276a37652 rcu/kvfree: Add debug check for GP complete for kfree_rcu_cpu list
  6b706e5603c4 rcu/kvfree: Make drain_page_cache() take early return if cache is disabled
  cdfa0f6fa6b7 rcu/kvfree: Add debug to check grace periods
  2e31da752c6d Merge branches 'doc.2023.05.10a', 'fixes.2023.05.11a', 'kvfree.2023.05.10a', 'nocb.2023.05.11a', 'rcu-tasks.2023.05.10a', 'torture.2023.05.15a' and 'rcu-urgent.2023.06.06a' into HEAD
  7e3f926bf453 rcu/kvfree: Eliminate k[v]free_rcu() single argument macro
  af96134dc856 Merge tag 'rcu.2023.06.22a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
  
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly ntfs3 report (Dec 2025) 0 (1) 2025/12/29 08:11
[syzbot] Monthly ntfs3 report (Nov 2025) 0 (1) 2025/11/27 07:44
[syzbot] Monthly ntfs3 report (Oct 2025) 0 (1) 2025/10/27 08:42
[syzbot] [ntfs3?] possible deadlock in mi_read (2) 0 (1) 2024/11/17 08:21
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in mi_read (2) origin:upstream 4 C 19 2d02h 366d 0/3 upstream: reported C repro on 2025/01/13 02:48
upstream possible deadlock in mi_read ntfs3 4 C error 11141 428d 1201d 28/29 fixed on 2024/11/12 23:31
linux-6.6 possible deadlock in mi_read 4 1 96d 96d 0/2 upstream: reported on 2025/10/10 02:42
linux-5.15 possible deadlock in mi_read origin:upstream missing-backport 4 C done 827 432d 1037d 3/3 fixed on 2024/12/22 10:18
linux-6.1 possible deadlock in mi_read origin:upstream missing-backport 4 C done 843 15d 1034d 0/3 upstream: reported C repro on 2023/03/17 09:05
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/12/19 08:58 19m retest repro upstream OK log
2025/12/19 06:39 22m retest repro upstream OK log
2025/12/19 06:39 24m retest repro upstream OK log
2025/12/19 06:39 24m retest repro upstream OK log
2025/12/19 06:39 22m retest repro upstream OK log
2025/12/19 06:39 24m retest repro upstream OK log
2025/12/18 00:06 20m retest repro upstream OK log
2025/12/18 00:06 20m retest repro upstream OK log
2025/12/18 00:06 20m retest repro upstream OK log
2025/12/18 00:06 20m retest repro upstream OK log

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.2.1411/9012 is trying to acquire lock:
ffff88804269f440 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
ffff88804269f440 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: mi_read+0x2d4/0x5a0 fs/ntfs3/record.c:148

but task is already holding lock:
ffff8880592eaf10 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
ffff8880592eaf10 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_link+0xf6/0x280 fs/ntfs3/namei.c:141

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&ni->ni_lock#2/5);
  lock(&ni->ni_lock#2/5);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

6 locks held by syz.2.1411/9012:
 #0: ffff888027f36480 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499
 #1: ffff8880592e83a8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1072 [inline]
 #1: ffff8880592e83a8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2864 [inline]
 #1: ffff8880592e83a8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2875 [inline]
 #1: ffff8880592e83a8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: filename_create+0x1fb/0x360 fs/namei.c:4879
 #2: ffff8880592eb1c8 (&sb->s_type->i_mutex_key#23){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline]
 #2: ffff8880592eb1c8 (&sb->s_type->i_mutex_key#23){+.+.}-{4:4}, at: vfs_link+0x3b4/0x6e0 fs/namei.c:5635
 #3: ffff8880592e80f0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline]
 #3: ffff8880592e80f0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_link+0xdb/0x280 fs/ntfs3/namei.c:139
 #4: ffff8880592eaf10 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
 #4: ffff8880592eaf10 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_link+0xf6/0x280 fs/ntfs3/namei.c:141
 #5: ffff888027f32120 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x163/0xd50 fs/ntfs3/fsntfs.c:571

stack backtrace:
CPU: 0 UID: 0 PID: 9012 Comm: syz.2.1411 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain kernel/locking/lockdep.c:3895 [inline]
 __lock_acquire+0x2540/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x107/0x340 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
 ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
 mi_read+0x2d4/0x5a0 fs/ntfs3/record.c:148
 mi_format_new+0x1a3/0x610 fs/ntfs3/record.c:434
 ni_add_subrecord+0xd1/0x460 fs/ntfs3/frecord.c:321
 ntfs_look_free_mft+0x6aa/0xd50 fs/ntfs3/fsntfs.c:715
 ni_create_attr_list+0x8ff/0x13d0 fs/ntfs3/frecord.c:828
 ni_ins_attr_ext+0x43f/0xba0 fs/ntfs3/frecord.c:926
 ni_insert_attr fs/ntfs3/frecord.c:1093 [inline]
 ni_insert_resident fs/ntfs3/frecord.c:1477 [inline]
 ni_add_name+0x6df/0xc90 fs/ntfs3/frecord.c:2923
 ntfs_link_inode+0x132/0x180 fs/ntfs3/inode.c:1738
 ntfs_link+0x118/0x280 fs/ntfs3/namei.c:146
 vfs_link+0x518/0x6e0 fs/namei.c:5646
 do_linkat+0x283/0x5a0 fs/namei.c:5716
 __do_sys_linkat fs/namei.c:5744 [inline]
 __se_sys_linkat fs/namei.c:5741 [inline]
 __x64_sys_linkat+0xd4/0xf0 fs/namei.c:5741
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb5c000f749
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb5bf65d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000109
RAX: ffffffffffffffda RBX: 00007fb5c0266090 RCX: 00007fb5c000f749
RDX: 0000000000000005 RSI: 0000200000000300 RDI: 0000000000000005
RBP: 00007fb5c0093f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000400 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb5c0266128 R14: 00007fb5c0266090 R15: 00007fff22f769f8
 </TASK>

Crashes (411):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/02 13:22 upstream b69053dd3ffb d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2026/01/02 10:26 upstream b69053dd3ffb d1b870e1 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2025/12/27 18:36 upstream c53f467229a7 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/11/17 05:50 upstream 7254a2b52279 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/11/15 16:28 upstream 7a0892d2836e f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/11/10 22:02 upstream 4ea7c1717f3f 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/11/07 15:23 upstream 4a0c9b339199 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/11/02 05:10 upstream 691d401c7e0e 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/28 03:28 upstream dcb6fa37fd7b fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in mi_read
2025/10/28 01:47 upstream fd57572253bc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/10/27 12:23 upstream dcb6fa37fd7b c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/10/27 10:40 upstream 4bb1f7e19c4a c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in mi_read
2025/10/27 08:58 upstream dcb6fa37fd7b c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/23 09:32 upstream 43e9ad0c55a3 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/21 15:07 upstream 6548d364a3e8 9832ed61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/18 00:23 upstream cf1ea8854e4f 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/12 16:06 upstream 67029a49db6c ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/08 11:15 upstream 971199ad2a0f 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/04 06:19 upstream 9b0d551bcc05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in mi_read
2025/10/04 00:50 upstream 9b0d551bcc05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/10/02 10:13 upstream 080ffb4bec4d 267f56c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/09/29 04:13 upstream 8f9736633f8c 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/09/25 13:47 upstream bf40f4b87761 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/09/16 16:55 upstream 46a51f4f5eda e2beed91 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2025/09/16 09:44 upstream 46a51f4f5eda e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/09/05 16:00 upstream d69eb204c255 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/08/27 01:12 upstream fab1beda7597 e12e5ba4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2025/05/03 01:22 upstream 2bfcee565c3a b0714e37 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2025/01/21 15:54 upstream 95ec54a420b8 6e87cfa2 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2025/01/21 15:02 upstream 95ec54a420b8 6e87cfa2 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2024/11/21 12:35 upstream 8f7c8b88bda4 4b25d554 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in mi_read
2026/01/10 00:26 upstream 54e82e93ca93 d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2026/01/02 09:40 upstream b69053dd3ffb d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/12/04 00:01 upstream 3f9f0252130e d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/12/02 11:37 upstream 1d18101a644e d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/11/26 15:24 upstream 30f09200cc4a c116feb4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/11/06 01:45 upstream dc77806cf3b4 a6c9c731 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/11/03 23:40 upstream 6146a0f1dfae e6c64ba8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/25 23:42 upstream 566771afc7a8 c0460fcd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/18 20:53 upstream f406055cb18c 1c8c8cd8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/18 14:10 upstream f406055cb18c 1c8c8cd8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/15 06:34 upstream 9b332cece987 b6605ba8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/10 14:10 upstream 5472d60c129f ff1712fe .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/06 04:04 upstream 6a74422b9710 49379ee0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/24 06:13 upstream cec1e6e5d1ab 0abd0691 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/20 19:20 upstream cd89d487374c 67c37560 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/16 15:58 upstream 46a51f4f5eda e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/15 21:48 upstream f83ec76bf285 e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/15 10:44 upstream 79e8447ec662 e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/14 02:36 upstream 5cd64d4f9268 e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/09 05:40 upstream f777d1112ee5 d291dd2d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/02 15:26 upstream b320789d6883 96a211bc .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2025/09/02 10:42 upstream b320789d6883 807a3b61 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/26 22:20 upstream fab1beda7597 e12e5ba4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2024/11/13 10:09 upstream 3022e9d00ebe 62026c85 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2024/11/13 08:45 upstream 3022e9d00ebe 62026c85 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in mi_read
2025/10/28 00:37 linux-next 8fec172c82c2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mi_read
2025/11/01 19:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci dcb6fa37fd7b 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mi_read
* Struck through repros no longer work on HEAD.