possible deadlock in attr_data_get_block (2)

Status: upstream: reported C repro on 2024/08/15 10:46
Subsystems: ntfs3
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+262a71e9d2faf8747085@syzkaller.appspotmail.com
First crash: 748d, last: 1h29m
Cause bisection: failed (error log, bisect log)
  
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
267c1761 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in attr_data_get_block (2) 2026/05/26 03:55 2026/05/26 03:55 2026/05/26 04:43 c69befb3
Discussions (20)
Title Replies (including bot) Last reply
[syzbot] Monthly ntfs3 report (Aug 2026) 0 (1) 2026/08/04 12:32
[PATCH 2/2] ntfs3: release ni_lock before dir_emit in ntfs_readdir to fix deadlocks 1 (1) 2026/07/01 01:30
[syzbot] Monthly ntfs3 report (Jun 2026) 0 (1) 2026/06/02 20:32
[syzbot] Monthly ntfs3 report (May 2026) 0 (1) 2026/05/02 12: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 (May 2025) 0 (1) 2025/05/24 10:04
[syzbot] Monthly ntfs3 report (Apr 2025) 0 (1) 2025/04/22 12:41
[syzbot] Monthly ntfs3 report (Mar 2025) 0 (1) 2025/03/18 14:49
[syzbot] Monthly ntfs3 report (Feb 2025) 0 (1) 2025/02/16 21:53
[syzbot] Monthly ntfs3 report (Jan 2025) 0 (1) 2025/01/15 08:54
[syzbot] Monthly ntfs3 report (Dec 2024) 0 (1) 2024/12/16 09:44
[syzbot] Monthly ntfs3 report (Nov 2024) 0 (1) 2024/11/13 11:07
[syzbot] Monthly ntfs3 report (Sep 2024) 0 (1) 2024/09/12 08:11
[syzbot] [ntfs3?] possible deadlock in attr_data_get_block (2) 0 (1) 2024/08/15 10:46
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in attr_data_get_block origin:upstream missing-backport 4 syz, C inconclusive 595 2d10h 1252d 0/3 upstream: reported C repro on 2023/03/29 04:32
linux-6.6 possible deadlock in attr_data_get_block origin:upstream missing-backport 4 syz, C error 110 24d 430d 0/2 upstream: reported C repro on 2025/06/27 20:24
upstream possible deadlock in attr_data_get_block ntfs3 4 syz, C error 3111 748d 1415d 27/29 fixed on 2024/08/14 03:44
linux-5.15 possible deadlock in attr_data_get_block origin:lts-only 4 syz, C done 424 37d 1253d 0/3 upstream: reported C repro on 2023/03/27 15:11
Last patch testing requests (9)
Created Duration User Patch Repo Result
2026/05/16 18:23 38m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci no crash log
2026/03/04 10:09 25m retest repro upstream no crash log
2026/03/04 10:09 21m retest repro upstream no crash log
2026/03/04 10:09 19m retest repro upstream no crash log
2026/03/04 10:09 28m retest repro upstream no crash log
2026/03/04 10:09 18m retest repro upstream no crash log
2026/03/04 05:02 25m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error
2026/03/04 04:52 25m retest repro upstream no crash log
2026/03/04 04:42 26m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.234/7137 is trying to acquire lock:
ffff888060b245d8 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
ffff888060b245d8 (&ni->ni_lock/5){+.+.}-{4:4}, at: attr_data_get_block+0x1cd/0x2c0 fs/ntfs3/attrib.c:976

but task is already holding lock:
ffff888060b24a70 (mapping.invalidate_lock#9){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
ffff888060b24a70 (mapping.invalidate_lock#9){.+.+}-{4:4}, at: filemap_fault+0x6e0/0x13c0 mm/filemap.c:3585

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (mapping.invalidate_lock#9){.+.+}-{4:4}:
       down_read+0x97/0x200 kernel/locking/rwsem.c:1574
       filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
       filemap_fault+0x6e0/0x13c0 mm/filemap.c:3585
       __do_fault+0x138/0x2a0 mm/memory.c:5565
       do_read_fault mm/memory.c:6000 [inline]
       do_fault mm/memory.c:6134 [inline]
       do_pte_missing+0x1828/0x28f0 mm/memory.c:4700
       handle_pte_fault mm/memory.c:6558 [inline]
       __handle_mm_fault mm/memory.c:6707 [inline]
       handle_mm_fault+0xf64/0x28c0 mm/memory.c:6876
       do_user_addr_fault+0xa4f/0x1340 arch/x86/mm/fault.c:1343
       handle_page_fault arch/x86/mm/fault.c:1483 [inline]
       exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595

-> #2 (vm_lock){++++}-{0:0}:
       __vma_start_exclude_readers+0x283/0x930 mm/mmap_lock.c:125
       __vma_start_write+0xdc/0x290 mm/mmap_lock.c:148
       vma_start_write include/linux/mmap_lock.h:303 [inline]
       mprotect_fixup+0x657/0xad0 mm/mprotect.c:836
       setup_arg_pages+0x658/0xbd0 fs/exec.c:675
       load_elf_binary+0xc6d/0x28f0 fs/binfmt_elf.c:1028
       search_binary_handler fs/exec.c:1759 [inline]
       exec_binprm fs/exec.c:1791 [inline]
       bprm_execve+0x930/0x1590 fs/exec.c:1847
       kernel_execve+0x8c3/0x9c0 fs/exec.c:1991
       try_to_run_init_process+0x13/0x60 init/main.c:1486
       kernel_init+0xb2/0x1d0 init/main.c:1616
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 (&mm->mmap_lock){++++}-{4:4}:
       down_read_killable+0xa4/0x220 kernel/locking/rwsem.c:1599
       mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:609
       get_mmap_lock_carefully mm/mmap_lock.c:450 [inline]
       lock_mm_and_find_vma+0x2d6/0x340 mm/mmap_lock.c:501
       do_user_addr_fault+0x343/0x1340 arch/x86/mm/fault.c:1366
       handle_page_fault arch/x86/mm/fault.c:1483 [inline]
       exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
       filldir+0x2bd/0x630 fs/readdir.c:-1
       dir_emit include/linux/fs.h:3607 [inline]
       ntfs_dir_emit fs/ntfs3/dir.c:388 [inline]
       ntfs_read_hdr+0x8a7/0xc10 fs/ntfs3/dir.c:429
       ntfs_readdir+0x9ab/0xf70 fs/ntfs3/dir.c:589
       iterate_dir+0x2f1/0x4e0 fs/readdir.c:110
       __do_sys_getdents fs/readdir.c:319 [inline]
       __se_sys_getdents+0xf1/0x270 fs/readdir.c:304
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->ni_lock/5){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3181 [inline]
       check_prevs_add kernel/locking/lockdep.c:3300 [inline]
       validate_chain kernel/locking/lockdep.c:3924 [inline]
       __lock_acquire+0x15ff/0x2e40 kernel/locking/lockdep.c:5254
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
       __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
       ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
       attr_data_get_block+0x1cd/0x2c0 fs/ntfs3/attrib.c:976
       ntfs_iomap_begin+0x4f0/0xf30 fs/ntfs3/inode.c:978
       iomap_iter_next include/linux/iomap.h:382 [inline]
       ntfs_iomap_next+0x5b6/0x880 fs/ntfs3/inode.c:2319
       iomap_iter+0xe2/0xec0 fs/iomap/iter.c:122
       iomap_read_folio+0x638/0x970 fs/iomap/buffered-io.c:675
       ntfs_read_folio+0x3f1/0x4b0 fs/ntfs3/inode.c:856
       filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2520
       filemap_fault+0xd12/0x13c0 mm/filemap.c:3689
       __do_fault+0x138/0x2a0 mm/memory.c:5565
       do_read_fault mm/memory.c:6000 [inline]
       do_fault mm/memory.c:6134 [inline]
       do_pte_missing+0x1828/0x28f0 mm/memory.c:4700
       handle_pte_fault mm/memory.c:6558 [inline]
       __handle_mm_fault mm/memory.c:6707 [inline]
       handle_mm_fault+0xf64/0x28c0 mm/memory.c:6876
       do_user_addr_fault+0xa4f/0x1340 arch/x86/mm/fault.c:1343
       handle_page_fault arch/x86/mm/fault.c:1483 [inline]
       exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595

other info that might help us debug this:

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

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(mapping.invalidate_lock#9);
                               lock(vm_lock);
                               lock(mapping.invalidate_lock#9);
  lock(&ni->ni_lock/5);

 *** DEADLOCK ***

locks held by syz.1.234/7137: 1, last CPU#1:
 #0: ffff888060b24a70 (mapping.invalidate_lock#9){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
 #0: ffff888060b24a70 (mapping.invalidate_lock#9){.+.+}-{4:4}, at: filemap_fault+0x6e0/0x13c0 mm/filemap.c:3585

stack backtrace:
CPU: 1 UID: 0 PID: 7137 Comm: syz.1.234 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2059
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2191
 check_prev_add kernel/locking/lockdep.c:3181 [inline]
 check_prevs_add kernel/locking/lockdep.c:3300 [inline]
 validate_chain kernel/locking/lockdep.c:3924 [inline]
 __lock_acquire+0x15ff/0x2e40 kernel/locking/lockdep.c:5254
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
 __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
 ni_lock fs/ntfs3/ntfs_fs.h:1247 [inline]
 attr_data_get_block+0x1cd/0x2c0 fs/ntfs3/attrib.c:976
 ntfs_iomap_begin+0x4f0/0xf30 fs/ntfs3/inode.c:978
 iomap_iter_next include/linux/iomap.h:382 [inline]
 ntfs_iomap_next+0x5b6/0x880 fs/ntfs3/inode.c:2319
 iomap_iter+0xe2/0xec0 fs/iomap/iter.c:122
 iomap_read_folio+0x638/0x970 fs/iomap/buffered-io.c:675
 ntfs_read_folio+0x3f1/0x4b0 fs/ntfs3/inode.c:856
 filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2520
 filemap_fault+0xd12/0x13c0 mm/filemap.c:3689
 __do_fault+0x138/0x2a0 mm/memory.c:5565
 do_read_fault mm/memory.c:6000 [inline]
 do_fault mm/memory.c:6134 [inline]
 do_pte_missing+0x1828/0x28f0 mm/memory.c:4700
 handle_pte_fault mm/memory.c:6558 [inline]
 __handle_mm_fault mm/memory.c:6707 [inline]
 handle_mm_fault+0xf64/0x28c0 mm/memory.c:6876
 do_user_addr_fault+0xa4f/0x1340 arch/x86/mm/fault.c:1343
 handle_page_fault arch/x86/mm/fault.c:1483 [inline]
 exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
RIP: 0033:0x7f23ef29cef9
Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 27 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 5b f3 0f bc c0 e9 30 01 00 00 66
RSP: 002b:00007f23ed515e58 EFLAGS: 00010287
RAX: 0000000000000040 RBX: 00007f23ed515ee0 RCX: 0000000000000000
RDX: 0000200000001040 RSI: 0000200000000f00 RDI: 0000200000001040
RBP: 0000200000000f40 R08: 0000200000000000 R09: 0000000000000000
R10: 0000200000000f40 R11: 0000000000000246 R12: 0000200000000f00
R13: 00007f23ed515ea0 R14: 0000000000000000 R15: 0000200000001040
 </TASK>

Crashes (3780):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/29 00:38 upstream c20313e98b04 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/26 01:18 upstream 66498c75b4f8 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/08/20 18:44 upstream a4ff2be345d0 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/15 10:02 upstream dac3e89a2c90 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/09 02:32 upstream a59f57e2aa12 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/08/06 13:56 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/06 10:27 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/06 08:01 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/06 00:13 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/05 22:59 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/02 23:22 upstream bd1dde877520 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/08/01 09:02 upstream 0131b508c0e2 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/27 07:22 upstream 4235cb24ec1e 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/26 23:52 upstream 4235cb24ec1e 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/26 20:02 upstream 3dab139d4795 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/26 00:48 upstream 3dab139d4795 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/25 19:59 upstream 0ce37745d4bf 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/24 07:49 upstream d326f83e819c 544adce9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/23 08:29 upstream 4539944e5151 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/21 18:52 upstream 248951ddc14d 7c5de9c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/21 13:18 upstream b95f03f04d47 7c5de9c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/21 03:52 upstream b95f03f04d47 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/19 19:08 upstream c6859eed755d 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/19 07:01 upstream 1229e2e57a5c 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/18 12:15 upstream af5e34a41cd6 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/17 15:17 upstream fce2dfa773ce 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/17 05:30 upstream fce2dfa773ce 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/17 03:56 upstream fce2dfa773ce 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/16 06:28 upstream 58717b2a1365 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/15 23:00 upstream 58717b2a1365 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/15 08:50 upstream 58717b2a1365 a4ed0f4f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/15 04:54 upstream 7059bdf4f04a 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/14 12:22 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/14 04:09 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/12 16:55 upstream 44696aa3a489 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/12 10:43 upstream 44696aa3a489 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/11 23:17 upstream dd3210c47e8d d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 23:57 upstream d96fcfe1b7f9 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 12:23 upstream a635d6748234 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 10:05 upstream 2c7c88a412aa 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/08 14:51 upstream 0e35b9b6ec0f 88a4b44c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/08 12:06 upstream 0e35b9b6ec0f ab40da58 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/07/07 16:35 upstream 0e35b9b6ec0f 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/07 06:45 upstream 0e35b9b6ec0f 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/07/06 16:11 upstream 8cdeaa50eae8 88b240e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/06 02:37 upstream f105f3631d51 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/05 14:28 upstream 7404ce516372 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/04 09:29 upstream 71dfdfb0209b fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/03 05:07 upstream 87320be9f0d2 58bf2096 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/01 13:29 upstream 665159e24674 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/30 16:50 upstream dc59e4fea9d8 00e8b0fd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/30 12:44 upstream dc59e4fea9d8 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/05/02 11:07 upstream f1a5e78a55eb a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2025/02/24 08:11 upstream d082ecbc71e9 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/09/13 10:33 upstream fdf042df0463 73e8a465 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/28 04:07 upstream 3ec3f5fc4a91 6c853ff9 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/28 02:49 upstream 3ec3f5fc4a91 6c853ff9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/15 01:11 upstream 9d5906799f7d e6b88e20 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/01/18 04:51 upstream 54e82e93ca93 d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in attr_data_get_block
2025/11/18 06:04 upstream e7c375b18160 ef766cd7 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in attr_data_get_block
2026/09/01 12:15 linux-next 89c07d98716a 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in attr_data_get_block
2026/05/27 07:55 linux-next e7e28506af98 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/08 18:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in attr_data_get_block
2025/10/11 19:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc ff1712fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in attr_data_get_block
* Struck through repros no longer work on HEAD.