syzbot


possible deadlock in attr_data_get_block

Status: upstream: reported C repro on 2023/03/29 04:32
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+f159b81656e067e7746b@syzkaller.appspotmail.com
First crash: 900d, last: 2d09h
Bug presence (1)
Date Name Commit Repro Result
2025/09/13 upstream (ToT) 22f20375f5b7 C [report] possible deadlock in attr_data_get_block
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in attr_data_get_block 4 21 15d 78d 0/2 upstream: reported on 2025/06/27 20:24
upstream possible deadlock in attr_data_get_block ntfs3 4 C error 3111 396d 1063d 27/29 fixed on 2024/08/14 03:44
linux-5.15 possible deadlock in attr_data_get_block origin:lts-only 4 C done 370 4d07h 901d 0/3 upstream: reported C repro on 2023/03/27 15:11
upstream possible deadlock in attr_data_get_block (2) ntfs3 4 C error 2788 now 394d 0/29 upstream: reported C repro on 2024/08/15 10:46
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/03/14 13:30 1h54m fix candidate upstream OK (0) job log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.18/4483 is trying to acquire lock:
ffff88806aeb6840 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ffff88806aeb6840 (&ni->ni_lock/5){+.+.}-{3:3}, at: attr_data_get_block+0x33b/0x1b70 fs/ntfs3/attrib.c:951

but task is already holding lock:
ffff88801d2aea58
 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:518

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xc2/0x120 mm/memory.c:5852
       _copy_to_user+0x27/0x130 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:169 [inline]
       ni_fiemap+0x4ec/0x1300 fs/ntfs3/frecord.c:2140
       ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1173
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x1425/0x1d10 fs/ioctl.c:810
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ni->ni_lock/5){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
       lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
       attr_data_get_block+0x33b/0x1b70 fs/ntfs3/attrib.c:951
       ntfs_file_mmap+0x448/0x6d0 fs/ntfs3/file.c:312
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_file+0x5d/0xb0 mm/util.c:1109
       __mmap_region mm/mmap.c:2772 [inline]
       mmap_region+0xe2c/0x1c70 mm/mmap.c:2916
       do_mmap+0x958/0xfd0 mm/mmap.c:1436
       vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:520
       ksys_mmap_pgoff+0x516/0x6f0 mm/mmap.c:1482
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

1 lock held by syz.1.18/4483:
 #0: ffff88801d2aea58 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff88801d2aea58 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:518

stack backtrace:
CPU: 0 PID: 4483 Comm: syz.1.18 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
 ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
 attr_data_get_block+0x33b/0x1b70 fs/ntfs3/attrib.c:951
 ntfs_file_mmap+0x448/0x6d0 fs/ntfs3/file.c:312
 call_mmap include/linux/fs.h:2270 [inline]
 mmap_file+0x5d/0xb0 mm/util.c:1109
 __mmap_region mm/mmap.c:2772 [inline]
 mmap_region+0xe2c/0x1c70 mm/mmap.c:2916
 do_mmap+0x958/0xfd0 mm/mmap.c:1436
 vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:520
 ksys_mmap_pgoff+0x516/0x6f0 mm/mmap.c:1482
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f755198ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f75528a9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f7551bc5fa0 RCX: 00007f755198ebe9
RDX: 00000000027fffff RSI: 0000000000600000 RDI: 0000200000000000
RBP: 00007f7551a11e19 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000004002011 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7551bc6038 R14: 00007f7551bc5fa0 R15: 00007ffe37f024a8
 </TASK>

Crashes (397):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/08 07:37 linux-6.1.y 28c695c365e1 d291dd2d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2024/03/05 23:03 linux-6.1.y a3eb3a74aa8c f39a7eed .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/12 00:46 linux-6.1.y 3db754f56897 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/09/07 16:50 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/09/04 19:16 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/08/22 09:20 linux-6.1.y 0bc96de781b4 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/08/11 21:53 linux-6.1.y 3594f306da12 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/08/07 13:04 linux-6.1.y 3594f306da12 04cffc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/08/04 20:40 linux-6.1.y 3594f306da12 f5bcc8dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/07/29 07:56 linux-6.1.y 3594f306da12 c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/07/28 21:04 linux-6.1.y 3594f306da12 6654ea9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/07/15 08:07 linux-6.1.y f2198ea7eb3e 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/07/04 05:37 linux-6.1.y 7e69c33e4858 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/07/02 10:07 linux-6.1.y 7e69c33e4858 bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/14 17:43 linux-6.1.y 58485ff1a74f 5f4b362d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/11 23:13 linux-6.1.y 58485ff1a74f 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/09 07:10 linux-6.1.y 58485ff1a74f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/04 20:28 linux-6.1.y 58485ff1a74f e565f08d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/02 18:38 linux-6.1.y da3c5173c55f b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/06/02 18:38 linux-6.1.y da3c5173c55f b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/05/26 04:10 linux-6.1.y da3c5173c55f 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
2025/09/11 22:16 linux-6.1.y 3db754f56897 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/08 14:46 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/07 15:15 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/05 08:10 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/04 20:59 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/04 10:39 linux-6.1.y f89b6e15694c d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/03 18:31 linux-6.1.y f89b6e15694c 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/01 20:50 linux-6.1.y f89b6e15694c 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/09/01 01:03 linux-6.1.y f89b6e15694c 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/30 23:09 linux-6.1.y f89b6e15694c 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/29 01:40 linux-6.1.y f89b6e15694c d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/27 16:19 linux-6.1.y 0bc96de781b4 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/20 04:24 linux-6.1.y 0bc96de781b4 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/15 16:44 linux-6.1.y 0bc96de781b4 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/14 20:22 linux-6.1.y 3594f306da12 5d8c2ac2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/12 21:28 linux-6.1.y 3594f306da12 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/08/09 20:07 linux-6.1.y 3594f306da12 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/07/28 05:23 linux-6.1.y 3594f306da12 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/07/22 07:47 linux-6.1.y 3369c6df2fae 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/07/15 19:32 linux-6.1.y f2198ea7eb3e 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/26 20:18 linux-6.1.y 58485ff1a74f 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/26 08:07 linux-6.1.y 58485ff1a74f 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/23 06:06 linux-6.1.y 58485ff1a74f d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/12 23:46 linux-6.1.y 58485ff1a74f 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/05 03:13 linux-6.1.y 58485ff1a74f 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/06/03 20:02 linux-6.1.y da3c5173c55f a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2025/05/29 23:37 linux-6.1.y da3c5173c55f 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in attr_data_get_block
2023/03/29 04:32 linux-6.1.y e3a87a10f259 fc067f05 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in attr_data_get_block
* Struck through repros no longer work on HEAD.