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: 225d, last: 8h09m
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 8d16h 165d 0/3 upstream: reported C repro on 2025/01/13 02:48
upstream possible deadlock in mi_read ntfs3 C error 11141 226d 999d 28/29 fixed on 2024/11/12 23:31
linux-5.15 possible deadlock in mi_read origin:upstream missing-backport C done 827 230d 836d 3/3 fixed on 2024/12/22 10:18
linux-6.1 possible deadlock in mi_read origin:upstream missing-backport C done 837 102d 832d 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 (309):
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/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/06/08 10:41 upstream 8630c59e9936 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/06 20:09 upstream e271ed52b344 9fa58bba .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/06 15:05 upstream e271ed52b344 9fa58bba .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/06/05 10:52 upstream 1af80d00e1e0 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/28 14:11 upstream feacb1774bd5 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/27 11:33 upstream 785cdec46e92 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/26 21:42 upstream 0ff41df1cb26 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/25 01:21 upstream b1427432d3b6 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/24 02:10 upstream eccf6f2f6ab9 f8cc0c83 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/23 18:56 upstream eccf6f2f6ab9 f8cc0c83 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/23 03:34 upstream 94305e83eccb fa44301a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/22 16:38 upstream d608703fcdd9 0919b50b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/22 02:55 upstream d608703fcdd9 0919b50b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/05/19 18:09 upstream a5806cd506af b84f0537 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs 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/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/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/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/08 09:12 upstream 8630c59e9936 4826c28e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/08 04:28 upstream 8630c59e9936 4826c28e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/07 20:37 upstream bdc7f8c5adad 4826c28e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/06/06 13:25 upstream e271ed52b344 3d899f2c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/30 19:02 upstream f66bc387efbe 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/30 17:52 upstream f66bc387efbe 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/30 16:05 upstream f66bc387efbe 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/29 20:57 upstream e0797d3b91de 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/29 17:30 upstream 90b83efa6701 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/28 17:44 upstream feacb1774bd5 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/27 16:18 upstream 914873bc7df9 874a1386 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/26 05:13 upstream d0c22de9995b 2d4582d0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/26 02:38 upstream d0c22de9995b 2d4582d0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/25 23:42 upstream d0c22de9995b 2d4582d0 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/24 14:43 upstream 4856ebd99715 ed351ea7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/24 03:40 upstream 7586ac7c340c ed351ea7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/23 14:55 upstream 94305e83eccb f8cc0c83 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/22 10:15 upstream d608703fcdd9 0919b50b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/20 15:11 upstream a5806cd506af b47f9e02 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/05/18 05:36 upstream 205b2bd7939c f41472b0 .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
* Struck through repros no longer work on HEAD.