syzbot


possible deadlock in ntfs_file_write_iter

Status: upstream: reported C repro on 2024/06/15 08:45
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+d7452fc408a961bcc6ec@syzkaller.appspotmail.com
First crash: 289d, last: 6d09h
Cause bisection: introduced by (bisect log) :
commit 69505fe98f198ee813898cbcaf6770949636430b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu May 30 07:54:07 2024 +0000

  fs/ntfs3: Replace inode_trylock with inode_lock

Crash: possible deadlock in ntfs_file_write_iter (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] possible deadlock in ntfs_file_write_iter 0 (3) 2024/08/03 08:04
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in ntfs_file_write_iter origin:lts-only C inconclusive 240 4d23h 220d 0/3 upstream: reported C repro on 2024/08/19 12:03
linux-6.1 possible deadlock in ntfs_file_write_iter origin:lts-only C 206 1d08h 236d 0/3 upstream: reported C repro on 2024/08/03 11:07
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/30 00:59 12m retest repro upstream report log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 Not tainted
------------------------------------------------------
syz-executor133/5844 is trying to acquire lock:
ffff88807d9e4258 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:153

but task is already holding lock:
ffff8880794a0398 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:835 [inline]
ffff8880794a0398 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: ntfs_file_write_iter+0x291/0x7a0 fs/ntfs3/file.c:1232

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       down_write+0x99/0x220 kernel/locking/rwsem.c:1577
       inode_lock include/linux/fs.h:815 [inline]
       ntfs_file_mmap+0x5bc/0x850 fs/ntfs3/file.c:377
       call_mmap include/linux/fs.h:2172 [inline]
       mmap_file mm/internal.h:123 [inline]
       __mmap_region mm/mmap.c:1453 [inline]
       mmap_region+0x1a2a/0x23f0 mm/mmap.c:1603
       do_mmap+0x8f0/0x1000 mm/mmap.c:496
       vm_mmap_pgoff+0x1dd/0x3d0 mm/util.c:588
       ksys_mmap_pgoff+0x4eb/0x720 mm/mmap.c:542
       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

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3161 [inline]
       check_prevs_add kernel/locking/lockdep.c:3280 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
       __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       down_read_killable+0xca/0xd30 kernel/locking/rwsem.c:1547
       mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:153
       get_mmap_lock_carefully mm/memory.c:6123 [inline]
       lock_mm_and_find_vma+0x29c/0x2f0 mm/memory.c:6174
       do_user_addr_fault arch/x86/mm/fault.c:1361 [inline]
       handle_page_fault arch/x86/mm/fault.c:1481 [inline]
       exc_page_fault+0x1bf/0x8c0 arch/x86/mm/fault.c:1539
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
       fault_in_readable+0x111/0x2d0
       fault_in_iov_iter_readable+0x229/0x280 lib/iov_iter.c:94
       generic_perform_write+0x259/0x6d0 mm/filemap.c:4044
       ntfs_file_write_iter+0x69c/0x7a0 fs/ntfs3/file.c:1259
       new_sync_write fs/read_write.c:590 [inline]
       vfs_write+0xaeb/0xd30 fs/read_write.c:683
       ksys_write+0x183/0x2b0 fs/read_write.c:736
       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

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sb->s_type->i_mutex_key#14);
                               lock(&mm->mmap_lock);
                               lock(&sb->s_type->i_mutex_key#14);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

3 locks held by syz-executor133/5844:
 #0: ffff888030e487f8 (&f->f_pos_lock){+.+.}-{3:3}, at: fdget_pos+0x24e/0x320 fs/file.c:1160
 #1: ffff88807d5b4420 (sb_writers#9){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2931 [inline]
 #1: ffff88807d5b4420 (sb_writers#9){.+.+}-{0:0}, at: vfs_write+0x225/0xd30 fs/read_write.c:679
 #2: ffff8880794a0398 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:835 [inline]
 #2: ffff8880794a0398 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: ntfs_file_write_iter+0x291/0x7a0 fs/ntfs3/file.c:1232

stack backtrace:
CPU: 1 UID: 0 PID: 5844 Comm: syz-executor133 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
 check_prev_add kernel/locking/lockdep.c:3161 [inline]
 check_prevs_add kernel/locking/lockdep.c:3280 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 down_read_killable+0xca/0xd30 kernel/locking/rwsem.c:1547
 mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:153
 get_mmap_lock_carefully mm/memory.c:6123 [inline]
 lock_mm_and_find_vma+0x29c/0x2f0 mm/memory.c:6174
 do_user_addr_fault arch/x86/mm/fault.c:1361 [inline]
 handle_page_fault arch/x86/mm/fault.c:1481 [inline]
 exc_page_fault+0x1bf/0x8c0 arch/x86/mm/fault.c:1539
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0010:fault_in_readable+0x111/0x2d0 mm/gup.c:2228
Code: 8b 6c 24 18 4c 89 ee 48 81 e6 ff 0f 00 00 31 ff e8 94 81 b6 ff 4c 89 e8 48 25 ff 0f 00 00 74 34 49 bf 00 00 00 00 00 fc ff df <41> 8a 5d 00 e8 96 7c b6 ff 43 0f b6 04 3e 84 c0 0f 85 61 01 00 00
RSP: 0018:ffffc90003d67a00 EFLAGS: 00050202
RAX: 00000000000008c2 RBX: 0000000020001946 RCX: ffff88802a450000
RDX: 0000000000000000 RSI: 00000000000008c2 RDI: 0000000000000000
RBP: ffffc90003d67ab8 R08: ffffffff81de6cfc R09: ffffffff84b29389
R10: 0000000000000002 R11: ffff88802a450000 R12: 0000000000000084
R13: 00000000200018c2 R14: 1ffff920007acf48 R15: dffffc0000000000
 fault_in_iov_iter_readable+0x229/0x280 lib/iov_iter.c:94
 generic_perform_write+0x259/0x6d0 mm/filemap.c:4044
 ntfs_file_write_iter+0x69c/0x7a0 fs/ntfs3/file.c:1259
 new_sync_write fs/read_write.c:590 [inline]
 vfs_write+0xaeb/0xd30 fs/read_write.c:683
 ksys_write+0x183/0x2b0 fs/read_write.c:736
 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:0x7efd54cd8dc9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efd54c8f218 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000000002c RCX: 00007efd54cd8dc9
RDX: 0000000000001006 RSI: 0000000020000940 RDI: 0000000000000005
RBP: 00007efd54d816c8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007efd54d816c0
R13: 00007efd54d4d83c R14: 00746e6572727563 R15: 7275632e73646970
 </TASK>
----------------
Code disassembly (best guess):
   0:	8b 6c 24 18          	mov    0x18(%rsp),%ebp
   4:	4c 89 ee             	mov    %r13,%rsi
   7:	48 81 e6 ff 0f 00 00 	and    $0xfff,%rsi
   e:	31 ff                	xor    %edi,%edi
  10:	e8 94 81 b6 ff       	call   0xffb681a9
  15:	4c 89 e8             	mov    %r13,%rax
  18:	48 25 ff 0f 00 00    	and    $0xfff,%rax
  1e:	74 34                	je     0x54
  20:	49 bf 00 00 00 00 00 	movabs $0xdffffc0000000000,%r15
  27:	fc ff df
* 2a:	41 8a 5d 00          	mov    0x0(%r13),%bl <-- trapping instruction
  2e:	e8 96 7c b6 ff       	call   0xffb67cc9
  33:	43 0f b6 04 3e       	movzbl (%r14,%r15,1),%eax
  38:	84 c0                	test   %al,%al
  3a:	0f 85 61 01 00 00    	jne    0x1a1

Crashes (94):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/16 07:42 upstream f868cd251776 cfe3a04a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/08/02 11:22 upstream c0ecd6388360 1e9c4cf3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/03/21 00:07 upstream 5fc319360819 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/03/14 01:01 upstream 4003c9e78778 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_file_write_iter
2025/03/13 17:29 upstream b7f94fcf5546 44be8b44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/03/11 10:27 upstream 4d872d51bc9d 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/03/09 21:45 upstream 1110ce6a1e34 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/02/28 15:57 upstream 76544811c850 67cf5345 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/02/28 07:54 upstream 1e15510b71c9 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/02/25 02:17 upstream d082ecbc71e9 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_file_write_iter
2025/02/17 07:01 upstream 224e74511041 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/02/07 19:25 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/02/01 23:21 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/01/20 09:39 upstream 9528d418de4d f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_file_write_iter
2025/01/11 14:18 upstream 77a903cd8e5a 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/01/11 06:31 upstream 2144da25584e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/01/04 18:09 upstream 63676eefb7a0 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_file_write_iter
2024/12/29 10:45 upstream 059dd502b263 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/27 21:01 upstream 8379578b11d5 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/26 15:47 upstream 9b2ffa6148b1 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_file_write_iter
2024/12/20 23:10 upstream e9b8ffafd20a d7f584ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/20 03:24 upstream baaa2567a712 5905cb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/20 00:49 upstream baaa2567a712 5905cb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/18 22:59 upstream aef25be35d23 a0626d3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/12/10 08:53 upstream 7cb1b4663150 cfc402b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/30 15:25 upstream 2ba9f676d0a2 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/30 01:28 upstream 509f806f7f70 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/29 23:35 upstream 509f806f7f70 5df23865 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/29 14:51 upstream 7af08b57bcb9 5df23865 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/26 07:53 upstream 9f16d5e6f220 11dbc254 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/18 16:31 upstream adc218676eef e7bb5d6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/16 04:58 upstream f868cd251776 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/11/08 23:35 upstream f1dce1f09380 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/10/14 23:00 upstream eca631b8fe80 b01b6661 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/10/08 17:44 upstream 87d6aab2389e 402f1df0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2024/10/04 06:19 upstream 0c559323bbaa d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_file_write_iter
2025/03/21 21:29 upstream d07de43e3f05 c6512ef7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ntfs_file_write_iter
2025/01/17 20:14 upstream 9bffa1ad25b8 bb91bdd4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ntfs_file_write_iter
2025/01/14 13:49 upstream c45323b7560e 0dce2409 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ntfs_file_write_iter
2024/12/10 13:48 linux-next af2ea8ab7a54 cfc402b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_file_write_iter
2024/06/11 08:43 linux-next a957267fa7e9 048c640a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_file_write_iter
2025/03/14 13:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 059f6cbcfa70 e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/02/28 09:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 017f704fbfb1 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/02/27 04:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a1c24ab82279 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/02/20 23:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e6747d19291c 50668798 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/02/16 05:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a64dcfb451e2 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/02/12 07:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/01/10 14:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 577490b6abb9 67d7ec0a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2025/01/01 06:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2024/12/01 18:26 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7b1d1d4cfac0 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2024/12/01 11:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7b1d1d4cfac0 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
2024/11/29 12:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7b1d1d4cfac0 5df23865 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_file_write_iter
* Struck through repros no longer work on HEAD.