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: 134d, last: 3h53m
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 9 11d 74d 0/3 upstream: reported C repro on 2025/01/13 02:48
upstream possible deadlock in mi_read ntfs3 C error 11141 135d 908d 28/28 fixed on 2024/11/12 23:31
linux-5.15 possible deadlock in mi_read origin:upstream missing-backport C done 827 139d 745d 3/3 fixed on 2024/12/22 10:18
linux-6.1 possible deadlock in mi_read origin:upstream missing-backport C done 837 11d 741d 0/3 upstream: reported C repro on 2023/03/17 09:05

Sample crash report:
ntfs3(loop0): Mark volume as dirty due to NTFS errors
ntfs3(loop0): Failed to load $Extend (-22).
ntfs3(loop0): Failed to initialize $Extend.
============================================
WARNING: possible recursive locking detected
6.13.0-syzkaller-00918-g95ec54a420b8 #0 Not tainted
--------------------------------------------
syz-executor192/5827 is trying to acquire lock:
ffff8880770b1e60 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
ffff8880770b1e60 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: mi_read+0x2e1/0x5a0 fs/ntfs3/record.c:148

but task is already holding lock:
ffff8880770b3468 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
ffff8880770b3468 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_rename+0x74a/0xd10 fs/ntfs3/namei.c:312

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-executor192/5827:
 #0: ffff88807c650420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:547
 #1: ffff8880771120f8 (&type->i_mutex_dir_key#6/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:867 [inline]
 #1: ffff8880771120f8 (&type->i_mutex_dir_key#6/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3215 [inline]
 #1: ffff8880771120f8 (&type->i_mutex_dir_key#6/1){+.+.}-{4:4}, at: do_renameat2+0x62c/0x13f0 fs/namei.c:5159
 #2: ffff8880770b3700 (&sb->s_type->i_mutex_key#14/4){+.+.}-{4:4}, at: vfs_rename+0x6a2/0xf00 fs/namei.c:5038
 #3: ffff888077111e60 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1115 [inline]
 #3: ffff888077111e60 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_rename+0x72f/0xd10 fs/ntfs3/namei.c:311
 #4: ffff8880770b3468 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
 #4: ffff8880770b3468 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_rename+0x74a/0xd10 fs/ntfs3/namei.c:312
 #5: ffff88804b5c8128 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x1e5/0x10c0 fs/ntfs3/fsntfs.c:571

stack backtrace:
CPU: 1 UID: 0 PID: 5827 Comm: syz-executor192 Not tainted 6.13.0-syzkaller-00918-g95ec54a420b8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_deadlock_bug+0x483/0x620 kernel/locking/lockdep.c:3037
 check_deadlock kernel/locking/lockdep.c:3089 [inline]
 validate_chain+0x15e2/0x5920 kernel/locking/lockdep.c:3891
 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
 __mutex_lock_common kernel/locking/mutex.c:585 [inline]
 __mutex_lock+0x1ac/0xee0 kernel/locking/mutex.c:735
 ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
 mi_read+0x2e1/0x5a0 fs/ntfs3/record.c:148
 mi_format_new+0x1ab/0x5d0 fs/ntfs3/record.c:429
 ni_add_subrecord+0xe2/0x430 fs/ntfs3/frecord.c:374
 ntfs_look_free_mft+0x878/0x10c0 fs/ntfs3/fsntfs.c:715
 ni_create_attr_list+0x9bd/0x1480 fs/ntfs3/frecord.c:878
 ni_ins_attr_ext+0x369/0xbe0 fs/ntfs3/frecord.c:976
 ni_insert_attr fs/ntfs3/frecord.c:1143 [inline]
 ni_insert_resident fs/ntfs3/frecord.c:1527 [inline]
 ni_add_name+0x809/0xe90 fs/ntfs3/frecord.c:3038
 ni_rename+0xc2/0x1e0 fs/ntfs3/frecord.c:3078
 ntfs_rename+0x7c1/0xd10 fs/ntfs3/namei.c:317
 vfs_rename+0xbdb/0xf00 fs/namei.c:5067
 do_renameat2+0xd94/0x13f0 fs/namei.c:5224
 __do_sys_rename fs/namei.c:5271 [inline]
 __se_sys_rename fs/namei.c:5269 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5269
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90c7ae77b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 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:00007ffec9028eb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f90c7ae77b9
RDX: 00007f90c7ae77b9 RSI: 0000000020000480 RDI: 0000000020000340
RBP: 00007f90c7b7a610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001

Crashes (189):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/03/24 06:26 upstream 586de92313fc 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/22 13:34 upstream 88d324e69ea9 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/19 20:36 upstream 81e4f8d68c66 e20d7b13 .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/03/16 22:05 upstream d1275e99d1c4 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/15 23:56 upstream 3571e8b091f4 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/15 16:03 upstream a29967be967e e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/15 10:04 upstream a29967be967e e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/09 06:46 upstream b7c90e3e717a 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/08 15:19 upstream 2a520073e74f 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/07 16:57 upstream 00a7d39898c8 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/07 07:33 upstream 0f52fd4f67c6 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/04 05:06 upstream 99fa936e8e4f c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/03/03 15:12 upstream 7eb172143d55 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/28 10:14 upstream 1e15510b71c9 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/28 05:12 upstream 1e15510b71c9 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/27 21:20 upstream dd83757f6e68 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/27 14:38 upstream dd83757f6e68 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/27 02:34 upstream 5394eea10651 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/25 03:24 upstream d082ecbc71e9 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/21 13:53 upstream 334426094588 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in mi_read
2025/02/20 13:25 upstream 87a132e73910 50668798 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in mi_read
2025/01/13 04:34 upstream be548645527a 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in mi_read
2025/03/28 03:10 upstream 4fa118e5b79f 6c09fb82 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/27 05:05 upstream f6e0150b2003 20510e88 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/26 20:18 upstream 1e26c5e28ca5 19e40f48 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/26 04:32 upstream 2df0c02dab82 89d30d73 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/22 04:01 upstream d07de43e3f05 c6512ef7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/22 04:00 upstream d07de43e3f05 c6512ef7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/21 13:27 upstream b3ee1e460951 62330552 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/20 13:46 upstream a7f2e10ecd8f 62330552 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/16 23:40 upstream cb82ca153949 e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/14 16:42 upstream e3a854b577cb e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/13 17:04 upstream b7f94fcf5546 44be8b44 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/10 18:03 upstream 80e54e84911a 16256247 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/10 05:59 upstream 80e54e84911a 163f510d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/08 07:51 upstream 21e4543a2e2f 7e3bd60d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/08 04:24 upstream 21e4543a2e2f 7e3bd60d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/04 14:42 upstream 99fa936e8e4f c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/03 20:40 upstream 7eb172143d55 c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/03 19:17 upstream 7eb172143d55 c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/03 12:56 upstream 7eb172143d55 c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/03 07:05 upstream 1973160c90d7 c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/02 14:37 upstream ece144f151ac c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/02 11:14 upstream ece144f151ac c3901742 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/23 20:26 upstream 27102b38b8ca d34966d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/22 01:59 upstream 8a61cb6e150e d34966d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/22 00:35 upstream 8a61cb6e150e d34966d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/20 10:04 upstream 87a132e73910 50668798 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/20 06:23 upstream 87a132e73910 50668798 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/02/19 03:19 upstream 6537cfb395f3 9a14138f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in mi_read
2025/03/28 01:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in mi_read
2025/01/24 16:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 521b0ce3 .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.