possible deadlock in ocfs2_read_virt_blocks

Status: upstream: reported C repro on 2024/12/22 11:42
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+3e2174c956a9427f8739@syzkaller.appspotmail.com
First crash: 600d, last: 2d21h
▶ ▼ Bug presence (2)
Date Name Commit Repro Result
2025/05/20 linux-5.15.y (ToT) a68c15152131 C [report] possible deadlock in ocfs2_read_virt_blocks
2025/05/20 upstream (ToT) a5806cd506af C Didn't crash
▶ ▼ Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ocfs2_read_virt_blocks origin:lts-only 4 syz, C inconclusive 548 15h02m 590d 0/3 upstream: reported C repro on 2025/01/01 05:39
upstream possible deadlock in ocfs2_read_virt_blocks ocfs2 4 1 701d 701d 0/29 auto-obsoleted due to no activity on 2024/12/21 05:39
▶ ▼ Last patch testing requests (3)
Created Duration User Patch Repo Result
2026/04/19 05:33 14m retest repro linux-5.15.y report log
2026/02/06 21:29 10m retest repro linux-5.15.y report log
2025/08/14 22:26 16m retest repro linux-5.15.y report log
▶ ▼ Fix bisection attempts (5)
Created Duration User Patch Repo Result
2026/03/28 07:32 1m fix candidate upstream error job log
2026/02/26 06:12 1m fix candidate upstream error job log
2026/01/24 06:54 1m fix candidate upstream error job log
2025/11/24 18:00 25m fix candidate upstream error job log
2025/05/27 12:01 3m fix candidate upstream error job log

Sample crash report:
ocfs2: Slot 0 on device (7,0) was already allocated to this node!
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
5.15.182-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor426/4260 is trying to acquire lock:
ffff0000e9d394a0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_read_virt_blocks+0x228/0x858 fs/ocfs2/extent_map.c:976

but task is already holding lock:
ffff0000c9476990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xecc/0x11a4 fs/jbd2/transaction.c:462

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (jbd2_handle){++++}-{0:0}:
       start_this_handle+0xef4/0x11a4 fs/jbd2/transaction.c:464
       jbd2__journal_start+0x28c/0x744 fs/jbd2/transaction.c:521
       jbd2_journal_start+0x3c/0x4c fs/jbd2/transaction.c:560
       ocfs2_start_trans+0x43c/0x794 fs/ocfs2/journal.c:354
       ocfs2_setattr+0x954/0x16c4 fs/ocfs2/file.c:1266
       notify_change+0xa08/0xcd8 fs/attr.c:505
       chown_common+0x42c/0x5a0 fs/open.c:680
       vfs_fchown fs/open.c:748 [inline]
       ksys_fchown+0xe0/0x158 fs/open.c:759
       __do_sys_fchown fs/open.c:767 [inline]
       __se_sys_fchown fs/open.c:765 [inline]
       __arm64_sys_fchown+0x7c/0x94 fs/open.c:765
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #2 (&journal->j_trans_barrier){.+.+}-{3:3}:
       down_read+0xc0/0x390 kernel/locking/rwsem.c:1498
       ocfs2_start_trans+0x430/0x794 fs/ocfs2/journal.c:352
       ocfs2_setattr+0x954/0x16c4 fs/ocfs2/file.c:1266
       notify_change+0xa08/0xcd8 fs/attr.c:505
       chown_common+0x42c/0x5a0 fs/open.c:680
       vfs_fchown fs/open.c:748 [inline]
       ksys_fchown+0xe0/0x158 fs/open.c:759
       __do_sys_fchown fs/open.c:767 [inline]
       __se_sys_fchown fs/open.c:765 [inline]
       __arm64_sys_fchown+0x7c/0x94 fs/open.c:765
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #1 (sb_internal#2){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1811 [inline]
       sb_start_intwrite include/linux/fs.h:1928 [inline]
       ocfs2_start_trans+0x2c4/0x794 fs/ocfs2/journal.c:350
       ocfs2_setattr+0x954/0x16c4 fs/ocfs2/file.c:1266
       notify_change+0xa08/0xcd8 fs/attr.c:505
       chown_common+0x42c/0x5a0 fs/open.c:680
       vfs_fchown fs/open.c:748 [inline]
       ksys_fchown+0xe0/0x158 fs/open.c:759
       __do_sys_fchown fs/open.c:767 [inline]
       __se_sys_fchown fs/open.c:765 [inline]
       __arm64_sys_fchown+0x7c/0x94 fs/open.c:765
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012
       lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
       down_read+0xc0/0x390 kernel/locking/rwsem.c:1498
       ocfs2_read_virt_blocks+0x228/0x858 fs/ocfs2/extent_map.c:976
       ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
       ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
       ocfs2_find_entry+0x314/0x1b84 fs/ocfs2/dir.c:1091
       ocfs2_rename+0x1840/0x2e98 fs/ocfs2/namei.c:1568
       vfs_rename+0x954/0xdcc fs/namei.c:4832
       do_renameat2+0x74c/0xcdc fs/namei.c:4985
       __do_sys_renameat2 fs/namei.c:5018 [inline]
       __se_sys_renameat2 fs/namei.c:5015 [inline]
       __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

other info that might help us debug this:

Chain exists of:
  &ocfs2_file_ip_alloc_sem_key --> &journal->j_trans_barrier --> jbd2_handle

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(jbd2_handle);
                               lock(&journal->j_trans_barrier);
                               lock(jbd2_handle);
  lock(&ocfs2_file_ip_alloc_sem_key);

 *** DEADLOCK ***

8 locks held by syz-executor426/4260:
 #0: ffff0000d729a460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff0000d729a748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: lock_rename fs/namei.c:3016 [inline]
 #1: ffff0000d729a748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: do_renameat2+0x30c/0xcdc fs/namei.c:4924
 #2: ffff0000e9d409c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #2: ffff0000e9d409c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_two_directories fs/namei.c:-1 [inline]
 #2: ffff0000e9d409c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3017 [inline]
 #2: ffff0000e9d409c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x388/0xcdc fs/namei.c:4924
 #3: ffff0000e9d39808 (&sb->s_type->i_mutex_key#20/5){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #3: ffff0000e9d39808 (&sb->s_type->i_mutex_key#20/5){+.+.}-{3:3}, at: do_renameat2+0x3bc/0xcdc fs/namei.c:4924
 #4: ffff0000e9d3a648 (&sb->s_type->i_mutex_key#21/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #4: ffff0000e9d3a648 (&sb->s_type->i_mutex_key#21/2){+.+.}-{3:3}, at: vfs_rename+0x60c/0xdcc fs/namei.c:4795
 #5: ffff0000d729a650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_rename+0x14d8/0x2e98 fs/ocfs2/namei.c:1488
 #6: ffff0000c9052ce8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x430/0x794 fs/ocfs2/journal.c:352
 #7: ffff0000c9476990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xecc/0x11a4 fs/jbd2/transaction.c:462

stack backtrace:
CPU: 0 PID: 4260 Comm: syz-executor426 Not tainted 5.15.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2011
 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012
 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
 down_read+0xc0/0x390 kernel/locking/rwsem.c:1498
 ocfs2_read_virt_blocks+0x228/0x858 fs/ocfs2/extent_map.c:976
 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
 ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
 ocfs2_find_entry+0x314/0x1b84 fs/ocfs2/dir.c:1091
 ocfs2_rename+0x1840/0x2e98 fs/ocfs2/namei.c:1568
 vfs_rename+0x954/0xdcc fs/namei.c:4832
 do_renameat2+0x74c/0xcdc fs/namei.c:4985
 __do_sys_renameat2 fs/namei.c:5018 [inline]
 __se_sys_renameat2 fs/namei.c:5015 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Crashes (388):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/16 01:06 linux-5.15.y 3b8db0e4f263 cfde8269 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (clean fs)] [mounted in repro #2 (clean fs)] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2026/08/11 21:50 linux-5.15.y aabd761612db 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/08/08 07:01 linux-5.15.y aabd761612db 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/08/04 05:26 linux-5.15.y 6e2fd6534337 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/08/01 02:18 linux-5.15.y 6e2fd6534337 7664cf44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/08/01 02:18 linux-5.15.y 6e2fd6534337 7664cf44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/30 13:40 linux-5.15.y 6e2fd6534337 2377cd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/28 17:21 linux-5.15.y 674f684f7c61 edc8a875 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/28 15:40 linux-5.15.y 674f684f7c61 edc8a875 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/28 07:20 linux-5.15.y 674f684f7c61 45ae1df4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/28 05:01 linux-5.15.y 674f684f7c61 45ae1df4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/28 03:03 linux-5.15.y 674f684f7c61 45ae1df4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/27 13:54 linux-5.15.y 674f684f7c61 aae9036b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/26 07:25 linux-5.15.y 674f684f7c61 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/25 22:52 linux-5.15.y 674f684f7c61 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/25 09:45 linux-5.15.y 674f684f7c61 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/25 03:07 linux-5.15.y 674f684f7c61 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/23 01:29 linux-5.15.y c86c4726e7f0 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/20 16:04 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/20 14:15 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/20 12:42 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/19 17:18 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/16 07:28 linux-5.15.y c86c4726e7f0 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/09 00:16 linux-5.15.y c86c4726e7f0 b9f1ceaa .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/08 12:20 linux-5.15.y c86c4726e7f0 88a4b44c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/07/06 01:03 linux-5.15.y c86c4726e7f0 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/26 00:05 linux-5.15.y eceeec79dbc6 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/25 22:43 linux-5.15.y eceeec79dbc6 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/22 22:22 linux-5.15.y eceeec79dbc6 5a630be6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/22 21:03 linux-5.15.y eceeec79dbc6 5a630be6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/18 16:08 linux-5.15.y dc027a595035 a776b0d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/10 14:59 linux-5.15.y dc027a595035 f79bac11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/06/06 19:31 linux-5.15.y dc027a595035 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/13 10:53 linux-5.15.y de8dfb3f0278 fec2a7ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/12 21:43 linux-5.15.y de8dfb3f0278 a0949470 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/11 03:36 linux-5.15.y de8dfb3f0278 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/07 13:57 linux-5.15.y ef251c45f1cd cbf9e0fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/06 18:18 linux-5.15.y ef251c45f1cd 1dddfd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/06 15:53 linux-5.15.y ef251c45f1cd 1dddfd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/06 13:19 linux-5.15.y ef251c45f1cd 1dddfd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/05 09:03 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/04 22:45 linux-5.15.y ef251c45f1cd a898ba9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/05/03 01:14 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/04/30 13:09 linux-5.15.y ef251c45f1cd a7464baf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/04/30 05:23 linux-5.15.y b9d57c40a767 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2026/04/29 23:57 linux-5.15.y b9d57c40a767 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2024/12/22 11:42 linux-5.15.y 91786f140358 b4fbdbd4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/26 22:27 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
* Struck through repros no longer work on HEAD.