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: 184d, last: 1d17h
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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in mi_read (2) origin:upstream C 11 12d 124d 0/3 upstream: reported C repro on 2025/01/13 02:48
upstream possible deadlock in mi_read ntfs3 C error 11141 185d 958d 28/28 fixed on 2024/11/12 23:31
linux-5.15 possible deadlock in mi_read origin:upstream missing-backport C done 827 189d 795d 3/3 fixed on 2024/12/22 10:18
linux-6.1 possible deadlock in mi_read origin:upstream missing-backport C done 837 61d 791d 0/3 upstream: reported C repro on 2023/03/17 09:05

Sample crash report:
ntfs3(loop0): ino=19, mi_enum_attr
ntfs3(loop0): Mark volume as dirty due to NTFS errors
============================================
WARNING: possible recursive locking detected
6.15.0-rc4-syzkaller-00189-g2bfcee565c3a #0 Not tainted
--------------------------------------------
syz-executor156/5819 is trying to acquire lock:
ffff88804bbe1e60 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
ffff88804bbe1e60 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: mi_read+0x2d4/0x5a0 fs/ntfs3/record.c:148

but task is already holding lock:
ffff88804bb40100 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
ffff88804bb40100 (&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-executor156/5819:
 #0: ffff88807d8c4420 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556
 #1: ffff88804bbe6a68 (&type->i_mutex_dir_key#6/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline]
 #1: ffff88804bbe6a68 (&type->i_mutex_dir_key#6/1){+.+.}-{4:4}, at: filename_create+0x1f9/0x470 fs/namei.c:4132
 #2: ffff88804bb40398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
 #2: ffff88804bb40398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: vfs_link+0x3b4/0x6e0 fs/namei.c:4838
 #3: ffff88804bbe67d0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1110 [inline]
 #3: ffff88804bbe67d0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_link+0xdb/0x280 fs/ntfs3/namei.c:139
 #4: ffff88804bb40100 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
 #4: ffff88804bb40100 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_link+0xf6/0x280 fs/ntfs3/namei.c:141
 #5: ffff88807d878128 (&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: 5819 Comm: syz-executor156 Not tainted 6.15.0-rc4-syzkaller-00189-g2bfcee565c3a #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3042
 check_deadlock kernel/locking/lockdep.c:3094 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3896
 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866
 __mutex_lock_common kernel/locking/mutex.c:601 [inline]
 __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746
 ni_lock fs/ntfs3/ntfs_fs.h:1105 [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:1698
 ntfs_link+0x118/0x280 fs/ntfs3/namei.c:146
 vfs_link+0x4ea/0x6e0 fs/namei.c:4847
 do_linkat+0x272/0x560 fs/namei.c:4917
 __do_sys_link fs/namei.c:4951 [inline]
 __se_sys_link fs/namei.c:4949 [inline]
 __x64_sys_link+0x82/0x90 fs/namei.c:4949
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb608ddde19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 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:00007ffeed9309c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000056
RAX: ffffffffffffffda RBX: 0000200000000080 RCX: 00007fb608ddde19
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 00002000000001c0
RBP: 0031656c69662f2e R08: 000055555860c4c0 R09: 000055555860c4c0
R10: 000055555860c4c0 R11: 0000000000000246 R12: 0030656c69662f2e
R13: 00007ffeed930c18 R14: 431bde82d7b634db R15: 00007fb608e2703b
 </TASK>

Crashes (253):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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/05/15 13:14 upstream c94d59a126cb d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/12 23:26 upstream 627277ba7c23 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/11 15:34 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/09 16:25 upstream 9c69f8884904 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/08 17:10 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/07 05:03 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/06 05:33 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/04 02:05 upstream 2a239ffbebb5 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/03 00:12 upstream 2bfcee565c3a b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/30 17:27 upstream b6ea1680d0ac 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/29 22:45 upstream ca91b9500108 aeb6ec69 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/04/26 16:28 upstream f1a3944c860b c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/23 15:06 upstream bc3372351d0c 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/21 03:16 upstream 6fea5fabd332 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/04 18:25 upstream e48e99b6edf4 1c4febdb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/03 20:50 upstream a2cc6ff5ec8f d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/04/02 08:03 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/03/31 08:14 upstream aa918db707fb d3999433 .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/05/07 12:05 upstream 0d8d44db295c 350f4ffc .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/07 08:02 upstream 0d8d44db295c 350f4ffc .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/06 14:37 upstream 01f95500a162 ae98e6b9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/04 10:03 upstream 2a239ffbebb5 b0714e37 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/29 02:28 upstream f15d97df5afa aeb6ec69 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/28 20:40 upstream f15d97df5afa aeb6ec69 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/27 13:54 upstream 5bc1018675ec c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/24 01:22 upstream a79be02bba5c 9882047a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/22 15:55 upstream a33b5a08cbbd 53a8b9bd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/22 07:04 upstream a33b5a08cbbd 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/21 12:40 upstream 9d7a0577c9db 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/21 09:40 upstream 9d7a0577c9db 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/20 08:43 upstream 119009db2674 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/19 19:13 upstream 8560697b23dc 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/19 09:19 upstream 3088d26962e8 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/19 03:01 upstream 3088d26962e8 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/16 15:30 upstream 1a1d569a75f3 a95239b1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/16 04:49 upstream 1a1d569a75f3 a95239b1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/10 09:26 upstream 3b07108ada81 988b336c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/09 12:50 upstream a24588245776 47d015b1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/08 04:29 upstream 0af2f6be1b42 a2ada0e7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/03 09:01 upstream a1b5bd45d4ee 996a9618 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/04/03 09:01 upstream a1b5bd45d4ee 996a9618 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/30 05:12 upstream 93d52288679e d3999433 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/28 23:18 upstream acb4f33713b9 9a1a9e31 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/31 11:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mi_read
2025/03/30 10:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mi_read
2025/03/29 12:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 cf25e2c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mi_read
2025/03/29 07:31 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 cf25e2c2 .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.