syzbot


possible deadlock in attr_data_get_block

Status: upstream: reported on 2025/06/27 20:24
Reported-by: syzbot+08019e91be38802a5b96@syzkaller.appspotmail.com
First crash: 3d15h, last: 14h00m
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in attr_data_get_block origin:lts-only C inconclusive 352 4d15h 825d 0/3 upstream: reported C repro on 2023/03/29 04:32
upstream possible deadlock in attr_data_get_block ntfs3 C error 3111 321d 988d 27/29 fixed on 2024/08/14 03:44
linux-5.15 possible deadlock in attr_data_get_block origin:lts-only C done 350 1d03h 826d 0/3 upstream: reported C repro on 2023/03/27 15:11
upstream possible deadlock in attr_data_get_block (2) ntfs3 C error 2362 1h54m 320d 0/29 upstream: reported C repro on 2024/08/15 10:46

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.6.95-syzkaller #0 Not tainted
------------------------------------------------------
syz.7.725/9342 is trying to acquire lock:
ffff88805c8d4360 (&ni->ni_lock#2/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
ffff88805c8d4360 (&ni->ni_lock#2/5){+.+.}-{3:3}, at: attr_data_get_block+0x2ed/0x1eb0 fs/ntfs3/attrib.c:918

but task is already holding lock:
ffff88807ef36a20 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
ffff88807ef36a20 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x168/0x400 mm/util.c:554

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xc6/0x120 mm/memory.c:5946
       _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:191 [inline]
       fiemap_fill_next_extent+0x1c1/0x390 fs/ioctl.c:145
       ni_fiemap+0x7e6/0xbe0 fs/ntfs3/frecord.c:2038
       ntfs_fiemap+0xdb/0x130 fs/ntfs3/file.c:1213
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x140c/0x1bb0 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:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ni->ni_lock#2/5){+.+.}-{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+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
       lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
       attr_data_get_block+0x2ed/0x1eb0 fs/ntfs3/attrib.c:918
       ntfs_file_mmap+0x4b8/0x730 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:2786 [inline]
       mmap_region+0xe57/0x1f80 mm/mmap.c:2937
       do_mmap+0x8d1/0xfd0 mm/mmap.c:1381
       vm_mmap_pgoff+0x1c0/0x400 mm/util.c:556
       ksys_mmap_pgoff+0x520/0x700 mm/mmap.c:1427
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 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#2/5);
                               lock(&mm->mmap_lock);
  lock(&ni->ni_lock#2/5);

 *** DEADLOCK ***

1 lock held by syz.7.725/9342:
 #0: ffff88807ef36a20 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
 #0: ffff88807ef36a20 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x168/0x400 mm/util.c:554

stack backtrace:
CPU: 0 PID: 9342 Comm: syz.7.725 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_noncircular+0x2bd/0x3c0 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+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
 ni_lock fs/ntfs3/ntfs_fs.h:1120 [inline]
 attr_data_get_block+0x2ed/0x1eb0 fs/ntfs3/attrib.c:918
 ntfs_file_mmap+0x4b8/0x730 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:2786 [inline]
 mmap_region+0xe57/0x1f80 mm/mmap.c:2937
 do_mmap+0x8d1/0xfd0 mm/mmap.c:1381
 vm_mmap_pgoff+0x1c0/0x400 mm/util.c:556
 ksys_mmap_pgoff+0x520/0x700 mm/mmap.c:1427
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f069518e929
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:00007f0696057038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f06953b5fa0 RCX: 00007f069518e929
RDX: 00000000027ffff7 RSI: 0000000000600000 RDI: 0000200000000000
RBP: 00007f0695210b39 R08: 0000000000000006 R09: 0000000000000000
R10: 0000000004012011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f06953b5fa0 R15: 00007fff4645d5c8
 </TASK>

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/30 21:34 linux-6.6.y 3f5b4c104b7d 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
2025/06/30 14:36 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
2025/06/27 23:30 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
2025/06/27 23:30 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
2025/06/27 20:24 linux-6.6.y 3f5b4c104b7d 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
2025/06/27 20:23 linux-6.6.y 3f5b4c104b7d 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in attr_data_get_block
* Struck through repros no longer work on HEAD.