syzbot


possible deadlock in ntfs_look_for_free_space

Status: upstream: reported C repro on 2024/11/08 07:38
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+d27edf9f96ae85939222@syzkaller.appspotmail.com
First crash: 282d, last: 9h06m
Cause bisection: failed (error log, bisect log)
  
Discussions (8)
Title Replies (including bot) Last reply
[syzbot] Monthly ntfs3 report (Jul 2025) 0 (1) 2025/07/25 12:39
[syzbot] Monthly ntfs3 report (Jun 2025) 0 (1) 2025/06/24 07:38
[syzbot] Monthly ntfs3 report (May 2025) 0 (1) 2025/05/24 10:04
[syzbot] Monthly ntfs3 report (Apr 2025) 0 (1) 2025/04/22 12:41
[syzbot] Monthly ntfs3 report (Mar 2025) 0 (1) 2025/03/18 14:49
[syzbot] Monthly ntfs3 report (Feb 2025) 0 (1) 2025/02/16 21:53
[syzbot] [ntfs3?] possible deadlock in ntfs_look_for_free_space 0 (3) 2025/01/31 10:55
[syzbot] Monthly ntfs3 report (Jan 2025) 0 (1) 2025/01/15 08:54
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in ntfs_look_for_free_space origin:upstream 4 C 16 1d10h 44d 0/2 upstream: reported C repro on 2025/06/30 18:00

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.16.0-syzkaller-06699-ge8d780dcd957 #0 Tainted: G        W          
------------------------------------------------------
syz-executor103/5895 is trying to acquire lock:
ffff888044bfa250 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362

but task is already holding lock:
ffff8880416f75d0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->file.run_lock#2){++++}-{4:4}:
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       down_read+0x97/0x1f0 kernel/locking/rwsem.c:1522
       run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1119
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x232b/0x37c0 fs/ntfs3/inode.c:540
       dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264
       ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85
       lookup_one_qstr_excl+0x131/0x360 fs/namei.c:1697
       do_unlinkat+0x1df/0x570 fs/namei.c:4638
       __do_sys_unlink fs/namei.c:4696 [inline]
       __se_sys_unlink fs/namei.c:4694 [inline]
       __x64_sys_unlink+0x47/0x50 fs/namei.c:4694
       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

-> #0 (&wnd->rw_lock){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       down_write_nested+0x3e/0x60 kernel/locking/rwsem.c:1691
       ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362
       attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159
       attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574
       ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512
       ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709
       ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1296
       ntfs_create+0x3d/0x50 fs/ntfs3/namei.c:110
       lookup_open fs/namei.c:3708 [inline]
       open_last_lookups fs/namei.c:3807 [inline]
       path_openat+0x1500/0x3840 fs/namei.c:4043
       do_filp_open+0x1fa/0x410 fs/namei.c:4073
       do_sys_openat2+0x121/0x1c0 fs/open.c:1435
       do_sys_open fs/open.c:1450 [inline]
       __do_sys_open fs/open.c:1458 [inline]
       __se_sys_open fs/open.c:1454 [inline]
       __x64_sys_open+0x11e/0x150 fs/open.c:1454
       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

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ni->file.run_lock#2);
                               lock(&wnd->rw_lock);
                               lock(&ni->file.run_lock#2);
  lock(&wnd->rw_lock);

 *** DEADLOCK ***

5 locks held by syz-executor103/5895:
 #0: ffff888044bf8488 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557
 #1: ffff8880415f9ae8 (&type->i_mutex_dir_key#6){++++}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #1: ffff8880415f9ae8 (&type->i_mutex_dir_key#6){++++}-{4:4}, at: open_last_lookups fs/namei.c:3804 [inline]
 #1: ffff8880415f9ae8 (&type->i_mutex_dir_key#6){++++}-{4:4}, at: path_openat+0x8e6/0x3840 fs/namei.c:4043
 #2: ffff8880415f9830 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline]
 #2: ffff8880415f9830 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_create_inode+0x16e/0x32a0 fs/ntfs3/inode.c:1204
 #3: ffff888044bfa118 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x163/0xd50 fs/ntfs3/fsntfs.c:571
 #4: ffff8880416f75d0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511

stack backtrace:
CPU: 0 UID: 0 PID: 5895 Comm: syz-executor103 Tainted: G        W           6.16.0-syzkaller-06699-ge8d780dcd957 #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043
 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 down_write_nested+0x3e/0x60 kernel/locking/rwsem.c:1691
 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362
 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159
 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574
 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512
 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709
 ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1296
 ntfs_create+0x3d/0x50 fs/ntfs3/namei.c:110
 lookup_open fs/namei.c:3708 [inline]
 open_last_lookups fs/namei.c:3807 [inline]
 path_openat+0x1500/0x3840 fs/namei.c:4043
 do_filp_open+0x1fa/0x410 fs/namei.c:4073
 do_sys_openat2+0x121/0x1c0 fs/open.c:1435
 do_sys_open fs/open.c:1450 [inline]
 __do_sys_open fs/open.c:1458 [inline]
 __se_sys_open fs/open.c:1454 [inline]
 __x64_sys_open+0x11e/0x150 fs/open.c:1454
 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:0x7fde85023499
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 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:00007ffc366140f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000200000000640 RCX: 00007fde85023499
RDX: 0000000000000000 RSI: 000000000014d27c RDI: 0000200000000180
RBP: 000020000001f840 R08: 002c6174656d776f R09: 00007ffc36614130
R10: 00007ffc36613fc0 R11: 0000000000000246 R12: 00007ffc3661411c
R13: 000000000000000c R14: 431bde82d7b634db R15: 00007ffc36614150
 </TASK>
ntfs3(loop0): ino=0, attr_set_size

Crashes (2631):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/31 06:11 upstream e8d780dcd957 f8f2b4da .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/01/31 10:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 4c6ac32f .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
2025/01/15 20:59 upstream 619f0b6fad52 7315a7cf .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/01/14 12:45 upstream c45323b7560e b1f1cd88 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/13 19:30 upstream 8742b2d8935f 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/13 05:10 upstream 0e39a731820a 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/12 09:22 upstream 53e760d89498 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/10 10:33 upstream 2b38afce25c4 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/09 23:50 upstream 561c80369df0 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/09 19:52 upstream 561c80369df0 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/09 16:47 upstream 0227b49b5027 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/09 01:42 upstream 37816488247d 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/08 19:13 upstream 37816488247d 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/08 16:06 upstream 37816488247d 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/08 05:31 upstream bec077162bd0 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/06 20:37 upstream 479058002c32 ffe1dd46 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/05 12:06 upstream 7e161a991ea7 904e669c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ntfs_look_for_free_space
2025/08/04 11:28 upstream d2eedaa3909b 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/04 05:10 upstream 352af6a011d5 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/04 00:16 upstream 352af6a011d5 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ntfs_look_for_free_space
2025/08/03 22:08 upstream 352af6a011d5 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/03 13:12 upstream 186f3edfdd41 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/02 21:47 upstream a6923c06a3b2 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/02 07:04 upstream a6923c06a3b2 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/02 02:07 upstream 0905809b38bd 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/01 15:58 upstream 89748acdf226 40127d41 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ntfs_look_for_free_space
2025/08/01 11:35 upstream f2d282e1dfb3 40127d41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/01 07:00 upstream f2d282e1dfb3 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/01 05:55 upstream f2d282e1dfb3 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/07/31 17:12 upstream 260f6f4fda93 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/07/31 17:12 upstream 260f6f4fda93 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/07/31 13:46 upstream 260f6f4fda93 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/07/31 05:48 upstream e8d780dcd957 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_look_for_free_space
2025/08/12 12:01 linux-next 2674d1eadaa2 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/12 00:10 linux-next b1549501188c 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/11 12:10 linux-next b1549501188c 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/10 00:52 linux-next b1549501188c 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/09 22:07 linux-next b1549501188c 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/08 09:19 linux-next b1549501188c 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/07 07:27 linux-next 442d93313cae 4bd24a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/07 05:06 linux-next b7d4e259682c 4bd24a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/05 07:31 linux-next afec768a6a8f abdcb213 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/04 19:17 linux-next 5c5a10f0be96 abdcb213 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/03 05:46 linux-next 84b92a499e7e 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/03 04:27 linux-next 84b92a499e7e 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2024/11/08 02:13 linux-next 74741a050b79 c069283c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2024/11/04 07:27 linux-next 1ffec08567f4 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_look_for_free_space
2025/08/10 17:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
2025/08/06 17:15 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 4bd24a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
2025/08/04 21:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 abdcb213 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
2025/08/04 16:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 abdcb213 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
2025/08/03 01:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 82af5ea7c611 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_look_for_free_space
* Struck through repros no longer work on HEAD.