syzbot


possible deadlock in filemap_fault

Status: upstream: reported C repro on 2022/11/03 22:14
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+7736960b837908f3a81d@syzkaller.appspotmail.com
First crash: 972d, last: 17h19m
Cause bisection: introduced by (bisect log) :
commit ad26a9c84510af7252e582e811de970433a9758f
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Oct 7 17:08:06 2022 +0000

  fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate

Crash: possible deadlock in filemap_fault (log)
Repro: C syz .config
  
Discussions (28)
Title Replies (including bot) Last reply
[syzbot] Monthly mm report (Jun 2025) 0 (1) 2025/06/13 12:25
[syzbot] Monthly mm report (May 2025) 0 (1) 2025/05/12 13:34
[syzbot] Monthly mm report (Apr 2025) 0 (1) 2025/04/09 07:11
[syzbot] Monthly mm report (Mar 2025) 0 (1) 2025/03/08 22:16
[syzbot] Monthly mm report (Feb 2025) 0 (1) 2025/02/05 12:44
[syzbot] Monthly mm report (Jan 2025) 0 (1) 2025/01/06 10:01
[syzbot] Monthly mm report (Dec 2024) 0 (1) 2024/12/05 09:04
[syzbot] Monthly mm report (Nov 2024) 1 (2) 2024/11/04 12:58
[syzbot] Monthly mm report (Oct 2024) 0 (1) 2024/10/03 09:02
[syzbot] Monthly mm report (Sep 2024) 0 (1) 2024/09/02 08:17
[syzbot] Monthly mm report (Aug 2024) 0 (1) 2024/08/02 16:15
[syzbot] Monthly mm report (Jul 2024) 0 (1) 2024/07/01 10:28
[syzbot] Monthly mm report (May 2024) 0 (1) 2024/05/31 06:48
[syzbot] Monthly mm report (Apr 2024) 0 (1) 2024/04/29 12:35
[syzbot] Monthly ntfs3 report (Apr 2024) 0 (1) 2024/04/05 12:38
[syzbot] Monthly mm report (Mar 2024) 0 (1) 2024/03/19 21:40
[syzbot] Monthly mm report (Feb 2024) 0 (1) 2024/02/17 20:23
[syzbot] possible deadlock in filemap_fault 0 (3) 2024/01/04 02:02
[syzbot] Monthly ntfs3 report (Jan 2024) 0 (1) 2024/01/02 13:36
[syzbot] Monthly mm report (Dec 2023) 0 (1) 2023/12/18 10:47
[syzbot] Monthly ntfs3 report (Dec 2023) 0 (1) 2023/12/02 14:45
[syzbot] Monthly ntfs3 report (Oct 2023) 0 (1) 2023/11/01 10:13
[syzbot] Monthly ntfs3 report (Sep 2023) 0 (1) 2023/10/02 09:42
[syzbot] Monthly ntfs3 report (Aug 2023) 0 (1) 2023/08/30 12:45
[syzbot] Monthly fat report (Jul 2023) 3 (4) 2023/07/14 23:29
[syzbot] Monthly fat report (May 2023) 0 (1) 2023/05/31 12:40
[syzbot] Monthly fat report (Apr 2023) 0 (1) 2023/05/01 09:05
[syzbot] Monthly fat report 0 (1) 2023/03/30 10:28
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in filemap_fault 84 659d 834d 0/3 auto-obsoleted due to no activity on 2023/11/17 20:19
linux-6.1 possible deadlock in filemap_fault (2) origin:upstream missing-backport C error 134 14d 554d 0/3 upstream: reported C repro on 2023/12/22 21:26
linux-6.1 possible deadlock in filemap_fault 192 661d 836d 0/3 auto-obsoleted due to no activity on 2023/11/15 23:38
linux-5.15 possible deadlock in filemap_fault (2) missing-backport origin:lts-only C error 57 1d19h 449d 0/3 upstream: reported C repro on 2024/04/06 04:54
Last patch testing requests (2)
Created Duration User Patch Repo Result
2023/09/12 12:00 24m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2023/07/14 17:41 17m nogikh@google.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.9.0-rc5-syzkaller-00042-ge88c4cfcb7b8 #0 Not tainted
------------------------------------------------------
syz-executor130/5083 is trying to acquire lock:
ffff88807a9ef3e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:850 [inline]
ffff88807a9ef3e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_fault+0x646/0x16a0 mm/filemap.c:3277

but task is already holding lock:
ffff888028038730 (&vma->vm_lock->lock){++++}-{3:3}, at: vma_start_read include/linux/mm.h:677 [inline]
ffff888028038730 (&vma->vm_lock->lock){++++}-{3:3}, at: lock_vma_under_rcu+0x2f9/0x730 mm/memory.c:5762

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&vma->vm_lock->lock){++++}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       down_write+0x3a/0x50 kernel/locking/rwsem.c:1579
       vma_start_write include/linux/mm.h:730 [inline]
       vma_link+0x2c6/0x550 mm/mmap.c:416
       insert_vm_struct+0x1a3/0x260 mm/mmap.c:3339
       __bprm_mm_init fs/exec.c:282 [inline]
       bprm_mm_init fs/exec.c:384 [inline]
       alloc_bprm+0x543/0xa00 fs/exec.c:1580
       kernel_execve+0x99/0xa10 fs/exec.c:2004
       try_to_run_init_process init/main.c:1373 [inline]
       kernel_init+0xe8/0x2b0 init/main.c:1500
       ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #2 (&mm->mmap_lock){++++}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       __might_fault+0xc6/0x120 mm/memory.c:6220
       _copy_to_user+0x2a/0xb0 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:191 [inline]
       fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145
       ni_fiemap+0xa5e/0x1230 fs/ntfs3/frecord.c:2065
       ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1206
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x1c09/0x2e50 fs/ioctl.c:838
       __do_sys_ioctl fs/ioctl.c:902 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&ni->file.run_lock#3){++++}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
       attr_data_get_block+0x2e3/0x2e10 fs/ntfs3/attrib.c:902
       ntfs_get_block_vbo+0x36a/0xd00 fs/ntfs3/inode.c:587
       do_mpage_readpage+0x829/0x1c80 fs/mpage.c:232
       mpage_read_folio+0x108/0x1e0 fs/mpage.c:399
       filemap_read_folio+0x1a2/0x790 mm/filemap.c:2331
       filemap_fault+0xed1/0x16a0 mm/filemap.c:3381
       __do_fault+0x137/0x460 mm/memory.c:4531
       do_shared_fault mm/memory.c:4954 [inline]
       do_fault mm/memory.c:5028 [inline]
       do_pte_missing mm/memory.c:3880 [inline]
       handle_pte_fault mm/memory.c:5300 [inline]
       __handle_mm_fault+0x2361/0x7240 mm/memory.c:5441
       handle_mm_fault+0x3c2/0x8a0 mm/memory.c:5606
       do_user_addr_fault arch/x86/mm/fault.c:1362 [inline]
       handle_page_fault arch/x86/mm/fault.c:1505 [inline]
       exc_page_fault+0x446/0x8e0 arch/x86/mm/fault.c:1563
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

-> #0 (mapping.invalidate_lock#3){.+.+}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869
       __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
       filemap_invalidate_lock_shared include/linux/fs.h:850 [inline]
       filemap_fault+0x646/0x16a0 mm/filemap.c:3277
       __do_fault+0x137/0x460 mm/memory.c:4531
       do_shared_fault mm/memory.c:4954 [inline]
       do_fault mm/memory.c:5028 [inline]
       do_pte_missing mm/memory.c:3880 [inline]
       handle_pte_fault mm/memory.c:5300 [inline]
       __handle_mm_fault+0x2361/0x7240 mm/memory.c:5441
       handle_mm_fault+0x3c2/0x8a0 mm/memory.c:5606
       do_user_addr_fault arch/x86/mm/fault.c:1362 [inline]
       handle_page_fault arch/x86/mm/fault.c:1505 [inline]
       exc_page_fault+0x446/0x8e0 arch/x86/mm/fault.c:1563
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

other info that might help us debug this:

Chain exists of:
  mapping.invalidate_lock#3 --> &mm->mmap_lock --> &vma->vm_lock->lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&vma->vm_lock->lock);
                               lock(&mm->mmap_lock);
                               lock(&vma->vm_lock->lock);
  rlock(mapping.invalidate_lock#3);

 *** DEADLOCK ***

1 lock held by syz-executor130/5083:
 #0: ffff888028038730 (&vma->vm_lock->lock){++++}-{3:3}, at: vma_start_read include/linux/mm.h:677 [inline]
 #0: ffff888028038730 (&vma->vm_lock->lock){++++}-{3:3}, at: lock_vma_under_rcu+0x2f9/0x730 mm/memory.c:5762

stack backtrace:
CPU: 0 PID: 5083 Comm: syz-executor130 Not tainted 6.9.0-rc5-syzkaller-00042-ge88c4cfcb7b8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
 check_noncircular+0x36a/0x4a0 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+0x18cb/0x58e0 kernel/locking/lockdep.c:3869
 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
 filemap_invalidate_lock_shared include/linux/fs.h:850 [inline]
 filemap_fault+0x646/0x16a0 mm/filemap.c:3277
 __do_fault+0x137/0x460 mm/memory.c:4531
 do_shared_fault mm/memory.c:4954 [inline]
 do_fault mm/memory.c:5028 [inline]
 do_pte_missing mm/memory.c:3880 [inline]
 handle_pte_fault mm/memory.c:5300 [inline]
 __handle_mm_fault+0x2361/0x7240 mm/memory.c:5441
 handle_mm_fault+0x3c2/0x8a0 mm/memory.c:5606
 do_user_addr_fault arch/x86/mm/fault.c:1362 [inline]
 handle_page_fault arch/x86/mm/fault.c:1505 [inline]
 exc_page_fault+0x446/0x8e0 arch/x86/mm/fault.c:1563
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7f65c30d889f
Code: a7 c5 09 00 0f 11 04 25 89 00 00 20 48 8b 35 78 a8 0c 00 e8 53 42 03 00 b8 33 00 00 00 48 89 ee 31 d2 66 0f 6f 05 21 c5 09 00 <66> 89 04 25 44 f7 01 20 bf 10 10 00 20 48 b8 2e 2f 66 69 6c 65 32
RSP: 002b:00007ffce9c3b740 EFLAGS: 00010246
RAX: 0000000000000033 RBX: 00007f65c3155066 RCX: 00007f65c310caf9
RDX: 0000000000000000 RSI: 00007f65c315504b RDI: 0000000000000004
RBP: 00007f65c315504b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f65c3155510
R13: 00007f65c3155055 R14: 23f2bfc581b02e40 R15: ad9a13bd00000000
 </TASK>

Crashes (2841):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/25 12:12 upstream e88c4cfcb7b8 8bdc0f22 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2024/01/03 08:06 upstream 610a9b8f49fb fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in filemap_fault
2024/12/08 09:03 upstream 7503345ac5f5 9ac0fdc6 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in filemap_fault
2022/12/06 18:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5541c0811a0 d88f3abb .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/06/28 18:09 upstream aaf724ed6926 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/28 08:43 upstream aaf724ed6926 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/27 12:49 upstream f02769e7f272 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/27 11:12 upstream 67a993863163 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/27 01:36 upstream e34a79b96ab9 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/26 23:18 upstream ee88bddf7f2f 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/26 00:05 upstream 92ca6c498a5e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/25 17:54 upstream 7595b66ae9de 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/24 22:38 upstream 78f4e737a53e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/24 21:14 upstream 78f4e737a53e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/24 03:35 upstream 78f4e737a53e e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/21 10:57 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/21 04:30 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/17 06:23 upstream 9afe652958c3 cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/16 22:17 upstream e04c78d86a96 d1716036 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/12 03:07 upstream 488ef3560196 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/11 07:45 upstream aef17cb3d3c4 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/10 15:10 upstream f09079bd04a9 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/10 05:31 upstream 19272b37aa4f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/07 12:07 upstream c0c9379f235d 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/07 06:14 upstream 7a912d04415b 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/06 14:02 upstream e271ed52b344 f61267d4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/05 15:44 upstream ec7714e49479 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/05 07:34 upstream 64980441d269 6b6b5f21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in filemap_fault
2025/06/04 21:05 upstream 1af80d00e1e0 e565f08d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/04 13:14 upstream 5abc7438f1e9 e565f08d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/04 04:53 upstream 5abc7438f1e9 a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/06/02 13:59 upstream cd2e103d57e5 b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/30 17:11 upstream f66bc387efbe 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/30 02:32 upstream e0797d3b91de 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/27 12:05 upstream 785cdec46e92 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/27 02:16 upstream 0ff41df1cb26 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/26 11:44 upstream 0ff41df1cb26 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/26 09:03 upstream 0f8c0258bf04 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/05/26 02:59 upstream 0f8c0258bf04 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in filemap_fault
2025/01/21 07:36 upstream 3d3a9c8b89d4 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in filemap_fault
2025/01/20 23:31 upstream 100ceb4817a2 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in filemap_fault
2025/01/19 21:19 upstream 9528d418de4d f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in filemap_fault
2025/01/19 20:18 upstream 9528d418de4d f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in filemap_fault
2025/01/14 09:46 upstream c45323b7560e b1f1cd88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in filemap_fault
2025/05/09 02:01 upstream 2c89c1b655c0 bb813bcc .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in filemap_fault
2024/06/14 19:28 upstream 2ccbdf43d5e7 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in filemap_fault
2025/01/20 09:38 upstream ffd294d346d1 f2cb035c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in filemap_fault
2023/10/06 12:57 upstream b78b18fb8ee1 db17ad9f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64 possible deadlock in filemap_fault
2025/06/11 07:24 linux-next 19a60293b992 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in filemap_fault
2025/06/10 08:47 linux-next b27cc623e01b 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in filemap_fault
2025/06/02 21:38 linux-next 3a83b350b5be b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in filemap_fault
2025/06/26 06:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9aa9b43d689e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/06/19 00:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 39dfc971e42d ca631f70 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/06/11 04:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/06/06 20:20 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e f61267d4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/06/02 20:57 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/05/28 05:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2025/05/27 07:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in filemap_fault
2022/10/30 22:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 2a71366b .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in filemap_fault
* Struck through repros no longer work on HEAD.