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: 326d, last: 1d20h
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 (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] possible deadlock in mi_read (2) 0 (1) 2024/11/17 08:21
Similar bugs (4)
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 16 1d17h 265d 0/3 upstream: reported C repro on 2025/01/13 02:48
upstream possible deadlock in mi_read ntfs3 4 C error 11141 327d 1100d 28/29 fixed on 2024/11/12 23:31
linux-5.15 possible deadlock in mi_read origin:upstream missing-backport 4 C done 827 331d 936d 3/3 fixed on 2024/12/22 10:18
linux-6.1 possible deadlock in mi_read origin:upstream missing-backport 4 C done 837 203d 933d 0/3 upstream: reported C repro on 2023/03/17 09:05
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/08/24 07:53 14m retest repro upstream report log
2025/08/24 07:53 15m retest repro upstream report log

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

but task is already holding lock:
ffff88804114bef0 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
ffff88804114bef0 (&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.19/6100:
 #0: ffff888026f52488 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557
 #1: ffff88804114b9e8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:915 [inline]
 #1: ffff88804114b9e8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0 fs/namei.c:4139
 #2: ffff88804114c1a8 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:870 [inline]
 #2: ffff88804114c1a8 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: vfs_link+0x3b4/0x6e0 fs/namei.c:4845
 #3: ffff88804114b730 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline]
 #3: ffff88804114b730 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_link+0xdb/0x280 fs/ntfs3/namei.c:139
 #4: ffff88804114bef0 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
 #4: ffff88804114bef0 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_link+0xf6/0x280 fs/ntfs3/namei.c:141
 #5: ffff88802695c118 (&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: 6100 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3895
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
 mi_read+0x2d4/0x5a0 fs/ntfs3/record.c:148
 mi_format_new+0x1a3/0x610 fs/ntfs3/record.c:434
 ni_add_subrecord+0xd0/0x440 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:826
 ni_ins_attr_ext+0x43e/0xb50 fs/ntfs3/frecord.c:924
 ni_insert_attr fs/ntfs3/frecord.c:1091 [inline]
 ni_insert_resident fs/ntfs3/frecord.c:1475 [inline]
 ni_add_name+0x6df/0xc90 fs/ntfs3/frecord.c:2987
 ntfs_link_inode+0x132/0x180 fs/ntfs3/inode.c:1728
 ntfs_link+0x118/0x280 fs/ntfs3/namei.c:146
 vfs_link+0x4ea/0x6e0 fs/namei.c:4854
 do_linkat+0x272/0x560 fs/namei.c:4924
 __do_sys_linkat fs/namei.c:4952 [inline]
 __se_sys_linkat fs/namei.c:4949 [inline]
 __x64_sys_linkat+0xd4/0xf0 fs/namei.c:4949
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7e89c5eba9
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:00007f7e892a5038 EFLAGS: 00000246 ORIG_RAX: 0000000000000109
RAX: ffffffffffffffda RBX: 00007f7e89ea6090 RCX: 00007f7e89c5eba9
RDX: 0000000000000005 RSI: 0000200000000300 RDI: 0000000000000005
RBP: 00007f7e89ce1e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000400 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7e89ea6128 R14: 00007f7e89ea6090 R15: 00007ffe9156bc98
 </TASK>

Crashes (366):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/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
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/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 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/09/05 09:58 upstream d69eb204c255 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/09/05 07:47 upstream d69eb204c255 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/08/29 06:48 upstream 07d9df80082b d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/07/22 16:15 upstream 89be9a83ccf1 8e9d1dc1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/07/16 01:18 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/07/14 00:48 upstream 5d5d62298b8b 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/29 16:03 upstream dfba48a70cb6 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/28 11:31 upstream 67a993863163 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/27 11:37 upstream f02769e7f272 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/26 15:27 upstream ee88bddf7f2f 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/23 08:11 upstream b67ec639010f d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/19 02:40 upstream 52da431bf03b ed3e87f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/14 05:17 upstream 02adc1490e6d 0e8da31f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/13 14:16 upstream 27605c8c0f69 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/17 02:35 upstream cb82ca153949 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-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/03 06:10 upstream e6b9dce0aeeb 96a211bc .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/27 16:38 upstream fab1beda7597 e12e5ba4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/26 21:13 upstream fab1beda7597 e12e5ba4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/10 07:41 upstream 561c80369df0 32a0e5ed .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/08 16:19 upstream bec077162bd0 56444e07 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/08/01 06:50 upstream d6084bb815c4 0c075d67 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/07/25 06:41 upstream 94ce1ac2c9b4 fb8f743d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/07/25 03:35 upstream 94ce1ac2c9b4 fb8f743d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/07/22 07:59 upstream 89be9a83ccf1 1555463b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/07/20 07:58 upstream bf61759db409 7117feec .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/07/02 04:35 upstream 66701750d556 bc80e4f0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/26 21:42 upstream ee88bddf7f2f 1ae8177e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/22 17:05 upstream 739a6c93cc75 d6cdfb8a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/13 09:41 upstream 27605c8c0f69 98683f8f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/12 08:01 upstream 488ef3560196 98683f8f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/11 08:31 upstream aef17cb3d3c4 5d7e17ca .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/10 18:02 upstream f09079bd04a9 5d7e17ca .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/09 18:34 upstream 19272b37aa4f 4826c28e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/29 21:18 linux-next 2aeda9592360 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in mi_read
2025/09/05 11:42 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b320789d6883 d291dd2d .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.