syzbot


possible deadlock in ntfs_fallocate

Status: upstream: reported C repro on 2022/12/09 08:57
Subsystems: ntfs3
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+adacb2b0c896bc427962@syzkaller.appspotmail.com
First crash: 1297d, last: 32d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
c7d5d367-df3b-41e1-8dd2-9fb3bfef79ca assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in ntfs_fallocate 2026/05/15 19:28 2026/05/15 19:28 2026/05/15 20:35 efdaf0f9b8bfc56ea6d17bea15a64f4591cc712d

			
		
Discussions (11)
Title Replies (including bot) Last reply
[syzbot] Monthly ntfs3 report (Jun 2026) 0 (1) 2026/06/02 20:32
[syzbot] Monthly ntfs3 report (Mar 2026) 0 (1) 2026/03/01 06:22
[syzbot] Monthly ntfs3 report (Jan 2026) 0 (1) 2026/01/28 22:39
[syzbot] Monthly ntfs3 report (Dec 2025) 0 (1) 2025/12/29 08:11
[syzbot] Monthly ntfs3 report (Nov 2025) 0 (1) 2025/11/27 07:44
[syzbot] Monthly ntfs3 report (Oct 2025) 0 (1) 2025/10/27 08:42
[syzbot] Monthly ntfs3 report (Sep 2025) 0 (1) 2025/09/25 16:00
[syzbot] Monthly ntfs3 report (Aug 2025) 0 (1) 2025/08/25 13:19
[syzbot] Monthly ntfs3 report (Sep 2024) 0 (1) 2024/09/12 08:11
[syzbot] possible deadlock in ntfs_fallocate 0 (2) 2024/09/11 02:39
[syzbot] Monthly ntfs3 report (Jul 2024) 0 (1) 2024/07/12 10:05
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in ntfs_fallocate (2) 4 1 94d 94d 0/2 upstream: reported on 2026/03/26 14:11
linux-6.1 possible deadlock in ntfs_fallocate origin:lts-only 4 C inconclusive 65 3d12h 949d 0/3 upstream: reported C repro on 2023/11/22 18:34
linux-6.6 possible deadlock in ntfs_fallocate 4 2 232d 331d 0/2 auto-obsoleted due to no activity on 2026/02/16 00:08
Last patch testing requests (7)
Created Duration User Patch Repo Result
2026/06/14 06:13 34m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2026/04/05 04:52 27m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error
2026/01/25 02:28 35m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error
2025/11/16 00:17 29m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2025/09/06 23:43 27m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2025/08/16 03:44 22m retest repro upstream OK log
2025/02/05 15:19 22m retest repro upstream OK log

Sample crash report:
loop2: detected capacity change from 0 to 4096
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.528/10819 is trying to acquire lock:
ffff88804057dd30 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
ffff88804057dd30 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7f3/0x1140 fs/ntfs3/file.c:690

but task is already holding lock:
ffff88804057e1b8 (mapping.invalidate_lock#9){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1083 [inline]
ffff88804057e1b8 (mapping.invalidate_lock#9){++++}-{4:4}, at: ntfs_fallocate+0x3c3/0x1140 fs/ntfs3/file.c:620

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (mapping.invalidate_lock#9){++++}-{4:4}:
       down_read+0x97/0x200 kernel/locking/rwsem.c:1537
       filemap_invalidate_lock_shared include/linux/fs.h:1093 [inline]
       filemap_fault+0x66f/0x12f0 mm/filemap.c:3537
       __do_fault+0x138/0x390 mm/memory.c:5323
       do_read_fault mm/memory.c:5758 [inline]
       do_fault mm/memory.c:5892 [inline]
       do_pte_missing+0x18d3/0x2e60 mm/memory.c:4404
       handle_pte_fault mm/memory.c:6276 [inline]
       __handle_mm_fault mm/memory.c:6414 [inline]
       handle_mm_fault+0xd0a/0x13c0 mm/memory.c:6583
       do_user_addr_fault+0x75b/0x1360 arch/x86/mm/fault.c:1385
       handle_page_fault arch/x86/mm/fault.c:1474 [inline]
       exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1527
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
       fault_in_readable+0x8e/0x130 mm/gup.c:-1
       fault_in_iov_iter_readable+0x1b4/0x2f0 lib/iov_iter.c:106
       generic_perform_write+0x765/0x8b0 mm/filemap.c:4363
       ntfs_file_write_iter+0x74b/0x870 fs/ntfs3/file.c:1319
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x629/0xba0 fs/read_write.c:688
       ksys_pwrite64 fs/read_write.c:795 [inline]
       __do_sys_pwrite64 fs/read_write.c:803 [inline]
       __se_sys_pwrite64 fs/read_write.c:800 [inline]
       __x64_sys_pwrite64+0x19c/0x230 fs/read_write.c:800
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&mm->mmap_lock){++++}-{4:4}:
       __might_fault+0xcb/0x130 mm/memory.c:7177
       _inline_copy_to_user include/linux/uaccess.h:201 [inline]
       _copy_to_user+0x2c/0xb0 lib/usercopy.c:26
       copy_to_user include/linux/uaccess.h:236 [inline]
       fiemap_fill_next_extent+0x1dd/0x3c0 fs/ioctl.c:144
       ni_fiemap+0x9a5/0xca0 fs/ntfs3/frecord.c:2009
       ntfs_fiemap+0x11d/0x1a0 fs/ntfs3/file.c:1420
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x126f/0x1540 fs/ioctl.c:531
       __do_sys_ioctl fs/ioctl.c:595 [inline]
       __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->ni_lock#2/5){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
       ntfs_fallocate+0x7f3/0x1140 fs/ntfs3/file.c:690
       vfs_fallocate+0x672/0x7f0 fs/open.c:340
       ksys_fallocate fs/open.c:364 [inline]
       __do_sys_fallocate fs/open.c:369 [inline]
       __se_sys_fallocate fs/open.c:367 [inline]
       __x64_sys_fallocate+0xc0/0x110 fs/open.c:367
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ni->ni_lock#2/5 --> &mm->mmap_lock --> mapping.invalidate_lock#9

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(mapping.invalidate_lock#9);
                               lock(&mm->mmap_lock);
                               lock(mapping.invalidate_lock#9);
  lock(&ni->ni_lock#2/5);

 *** DEADLOCK ***

3 locks held by syz.2.528/10819:
 #0: ffff888036ffe480 (sb_writers#27){++++}-{0:0}, at: file_start_write include/linux/fs.h:2710 [inline]
 #0: ffff888036ffe480 (sb_writers#27){++++}-{0:0}, at: vfs_fallocate+0x5f9/0x7f0 fs/open.c:339
 #1: ffff88804057dfe8 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1028 [inline]
 #1: ffff88804057dfe8 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: ntfs_fallocate+0x2f1/0x1140 fs/ntfs3/file.c:606
 #2: ffff88804057e1b8 (mapping.invalidate_lock#9){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1083 [inline]
 #2: ffff88804057e1b8 (mapping.invalidate_lock#9){++++}-{4:4}, at: ntfs_fallocate+0x3c3/0x1140 fs/ntfs3/file.c:620

stack backtrace:
CPU: 0 UID: 0 PID: 10819 Comm: syz.2.528 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 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 kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
 ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline]
 ntfs_fallocate+0x7f3/0x1140 fs/ntfs3/file.c:690
 vfs_fallocate+0x672/0x7f0 fs/open.c:340
 ksys_fallocate fs/open.c:364 [inline]
 __do_sys_fallocate fs/open.c:369 [inline]
 __se_sys_fallocate fs/open.c:367 [inline]
 __x64_sys_fallocate+0xc0/0x110 fs/open.c:367
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f767b6bbf79
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:00007f7679916028 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f767b935fa0 RCX: 00007f767b6bbf79
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 00007f767b7527e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f767b936038 R14: 00007f767b935fa0 R15: 00007ffc8cd3aac8
 </TASK>

Crashes (523):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/15 18:49 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/02/10 05:29 upstream 8a5203c630c6 4ab09a02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/02/07 08:17 upstream 2687c848e578 f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/31 17:43 upstream ad9a728a3388 afc0c4d4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/29 12:42 upstream 8dfce8991b95 aeb6fdd5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/26 12:53 upstream 63804fed149a a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/05 10:51 upstream 3609fa95fb0f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/05 05:39 upstream 54e82e93ca93 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_fallocate
2026/01/03 01:15 upstream 9b0436804460 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/01/02 04:13 upstream b69053dd3ffb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/29 07:39 upstream c875a6c32467 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/26 00:21 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/25 06:38 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/20 13:54 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/13 06:56 upstream 9551a26f17d9 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/10 02:16 upstream cb015814f8b6 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/12/09 13:59 upstream cfd4039213e7 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/11/01 01:28 upstream 58fdd8484c05 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/30 00:45 upstream e53642b87a4f fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/27 18:23 upstream dcb6fa37fd7b fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/24 16:49 upstream 6fab32bb6508 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/21 13:42 upstream 6548d364a3e8 9832ed61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/08 20:13 upstream 0d97f2067c16 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/10/05 06:43 upstream d104e3d17f7b 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/09/13 20:57 upstream 5cd64d4f9268 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_fallocate
2025/08/23 20:29 upstream 8d245acc1e88 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/08/23 00:03 upstream cf6fc5eefc5b bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/08/02 02:45 upstream 0905809b38bd 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/08/01 07:18 upstream f2d282e1dfb3 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/08/01 00:10 upstream 260f6f4fda93 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/27 06:50 upstream 302f88ff3584 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/27 02:12 upstream 302f88ff3584 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/24 15:26 upstream 25fae0b93d1d 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/24 09:16 upstream 01a412d06bc5 0c1d6ded .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_fallocate
2025/07/23 03:07 upstream 89be9a83ccf1 8e9d1dc1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/20 19:53 upstream f4a40a4282f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/07/19 20:48 upstream 4871b7cb27f4 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2025/04/22 19:18 upstream a33b5a08cbbd 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in ntfs_fallocate
2024/09/11 02:38 upstream 8d8d276ba2fb 86aa7bd7 .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_fallocate
2024/05/08 13:25 upstream dccb07f2914c 4cf3f9b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ntfs_fallocate
2024/04/24 11:03 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ntfs_fallocate
2025/10/30 18:39 upstream e53642b87a4f 2c50b6a9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ntfs_fallocate
2024/05/07 13:03 upstream dccb07f2914c cb2dcc0e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in ntfs_fallocate
2022/12/09 03:02 upstream f3e8416619ce 1034e5fa .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_fallocate
2026/05/27 08:01 linux-next e7e28506af98 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_fallocate
2025/12/06 06:50 linux-next 6987d58a9cbc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_fallocate
2025/08/01 09:28 linux-next 84b92a499e7e 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_fallocate
2025/08/01 08:18 linux-next 84b92a499e7e 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_fallocate
2025/11/26 08:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b5fb0949b675 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/10/13 21:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/10/11 18:25 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/09/27 06:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2213e57a69f0 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/09/22 11:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 506ba4ea4cf5 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/08/23 06:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 bf27483f .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
2025/08/23 04:42 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ntfs_fallocate
* Struck through repros no longer work on HEAD.