syzbot


possible deadlock in ntfs_fiemap

Status: upstream: reported C repro on 2025/07/08 21:32
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+349ef4875b811300cb58@syzkaller.appspotmail.com
First crash: 374d, last: 15d
Bug presence (2)
Date Name Commit Repro Result
2025/10/08 linux-6.6.y (ToT) e617101e5626 C [report] possible deadlock in ntfs_fiemap
2025/10/08 upstream (ToT) a8cdf51cda30 C Didn't crash
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ntfs_fiemap ntfs3 4 C error inconclusive 5669 149d 1325d 0/29 auto-obsoleted due to no activity on 2026/05/14 08:44
linux-6.1 possible deadlock in ntfs_fiemap origin:lts-only 4 C inconclusive 485 5d01h 1208d 0/3 upstream: reported C repro on 2023/03/28 04:41
linux-5.15 possible deadlock in ntfs_fiemap origin:lts-only 4 C error 48 171d 1206d 0/3 upstream: reported C repro on 2023/03/30 02:33
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2026/06/28 03:15 2h02m fix candidate upstream OK (0) job log
2026/03/27 03:00 10m fix candidate upstream error job log
2026/02/23 14:50 1m fix candidate upstream error job log
2026/01/24 08:18 1m fix candidate upstream error job log

Sample crash report:
syz.0.17[5934]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
loop0: detected capacity change from 0 to 4096
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/5934 is trying to acquire lock:
ffff88802426baa0 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xaa/0x120 mm/memory.c:5968

but task is already holding lock:
ffff88807140ad40 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
ffff88807140ad40 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ntfs_fiemap+0xc8/0x130 fs/ntfs3/file.c:1218

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->ni_lock#3/5){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x135/0xc80 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
       attr_data_get_block+0x31a/0x2000 fs/ntfs3/attrib.c:920
       ntfs_file_mmap+0x4e7/0x7a0 fs/ntfs3/file.c:294
       call_mmap include/linux/fs.h:2023 [inline]
       mmap_file mm/internal.h:98 [inline]
       __mmap_region mm/mmap.c:2790 [inline]
       mmap_region+0xfa2/0x2090 mm/mmap.c:2941
       do_mmap+0x98f/0x10a0 mm/mmap.c:1385
       vm_mmap_pgoff+0x1c4/0x3f0 mm/util.c:556
       ksys_mmap_pgoff+0x4c9/0x720 mm/mmap.c:1431
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137
       lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
       __might_fault+0xc6/0x120 mm/memory.c:5968
       _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:191 [inline]
       fiemap_fill_next_extent+0x1de/0x3b0 fs/ioctl.c:145
       ni_fiemap+0x97a/0xc70 fs/ntfs3/frecord.c:2062
       ntfs_fiemap+0xdb/0x130 fs/ntfs3/file.c:1220
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x14fe/0x1cc0 fs/ioctl.c:811
       __do_sys_ioctl fs/ioctl.c:869 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ni->ni_lock#3/5);
                               lock(&mm->mmap_lock);
                               lock(&ni->ni_lock#3/5);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.0.17/5934:
 #0: ffff88807140ad40 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
 #0: ffff88807140ad40 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ntfs_fiemap+0xc8/0x130 fs/ntfs3/file.c:1218

stack backtrace:
CPU: 0 PID: 5934 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 __might_fault+0xc6/0x120 mm/memory.c:5968
 _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
 copy_to_user include/linux/uaccess.h:191 [inline]
 fiemap_fill_next_extent+0x1de/0x3b0 fs/ioctl.c:145
 ni_fiemap+0x97a/0xc70 fs/ntfs3/frecord.c:2062
 ntfs_fiemap+0xdb/0x130 fs/ntfs3/file.c:1220
 ioctl_fiemap fs/ioctl.c:220 [inline]
 do_vfs_ioctl+0x14fe/0x1cc0 fs/ioctl.c:811
 __do_sys_ioctl fs/ioctl.c:869 [inline]
 __se_sys_ioctl+0x83/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcee299ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe44530348 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fcee2c15fa0 RCX: 00007fcee299ce59
RDX: 0000200000000340 RSI: 00000000c020660b RDI: 0000000000000006
RBP: 00007fcee2a32e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcee2c15fac R14: 00007fcee2c15fa0 R15: 00007fcee2c15fa0
 </TASK>

Crashes (83):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/06/27 17:11 linux-6.6.y d1cfde2d5d15 fb92f11c .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/10/07 20:03 linux-6.6.y e617101e5626 8ef35d49 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/07/03 08:40 linux-6.6.y d1cfde2d5d15 58bf2096 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/05/26 11:15 linux-6.6.y 0a40c6fbd105 a3e47276 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/05/08 03:08 linux-6.6.y 258cf62a6dfd 5633175a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/05/02 13:17 linux-6.6.y 258cf62a6dfd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/04/24 02:36 linux-6.6.y 9760bf04666d 9cfb3ca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/04/11 17:03 linux-6.6.y 8cee53b8eaeb 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/27 15:02 linux-6.6.y c09fbcd31ae6 74a13a23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/26 14:05 linux-6.6.y c09fbcd31ae6 766b6434 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/23 14:47 linux-6.6.y 4fc00fe35d46 4933dba2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/23 09:29 linux-6.6.y 4fc00fe35d46 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/17 23:41 linux-6.6.y 4fc00fe35d46 c8810548 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/16 22:56 linux-6.6.y 4fc00fe35d46 0737c18f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/03/03 03:23 linux-6.6.y 7a137e9bfa0e 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/02/28 05:20 linux-6.6.y 7a137e9bfa0e 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/02/05 15:37 linux-6.6.y 2cf6f68313dc 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/02/01 06:14 linux-6.6.y 2cf6f68313dc 6b8752f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/28 03:05 linux-6.6.y cbb31f77b879 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/26 16:00 linux-6.6.y cbb31f77b879 a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/24 15:59 linux-6.6.y cbb31f77b879 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/24 03:12 linux-6.6.y cbb31f77b879 4f25b9b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/21 21:27 linux-6.6.y cbb31f77b879 8fc37797 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/20 17:45 linux-6.6.y cbb31f77b879 06648d9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/17 03:10 linux-6.6.y c596736dadab 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/10 12:32 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/07 17:19 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/05 17:22 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2026/01/03 19:00 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/29 11:04 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/28 13:29 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/27 16:51 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/22 03:23 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/16 11:44 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/16 03:40 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/09 20:10 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/12/01 17:11 linux-6.6.y 4791134e4aeb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/25 04:15 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/25 04:12 linux-6.6.y 1e89a1be4fe9 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/22 01:32 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/22 01:32 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/19 15:12 linux-6.6.y 0a805b6ea8cd 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/17 16:52 linux-6.6.y 0a805b6ea8cd ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/11/17 07:29 linux-6.6.y 0a805b6ea8cd f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/08/01 22:09 linux-6.6.y 3a8ababb8b6a 40127d41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/17 17:47 linux-6.6.y 9247f4e6573a 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/15 08:20 linux-6.6.y 9247f4e6573a 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/14 22:24 linux-6.6.y 9247f4e6573a d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/10 06:09 linux-6.6.y a5df3a702b2c 956bd956 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/10 06:06 linux-6.6.y a5df3a702b2c 956bd956 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
2025/07/08 21:32 linux-6.6.y a5df3a702b2c 4d9fdfa4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in ntfs_fiemap
* Struck through repros no longer work on HEAD.