syzbot

 sign-in | mailing list | source | docs
🐞 Open [828]
🐞 Fixed [84]
🐞 Invalid [1080]
⬇ Missing Backports [128]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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: 318d, last: 1h22m
▶ ▼ 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 C inconclusive 380 1d13h 308d 0/3 upstream: reported C repro on 2025/01/01 05:39
upstream possible deadlock in ocfs2_read_virt_blocks ocfs2 4 1 419d 419d 0/29 auto-obsoleted due to no activity on 2024/12/21 05:39
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/08/14 22:26 16m retest repro linux-5.15.y report log
▶ ▼ Fix bisection attempts (1)
Created Duration User Patch Repo Result
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 (248):
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
2025/11/05 11:29 linux-5.15.y cc5ec8769306 a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/11/03 09:03 linux-5.15.y cc5ec8769306 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/27 15:59 linux-5.15.y ac56c046adf4 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/23 15:01 linux-5.15.y ac56c046adf4 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/17 16:00 linux-5.15.y 29e53a5b1c4f 7adf5298 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/15 21:22 linux-5.15.y 29e53a5b1c4f 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/13 15:34 linux-5.15.y 29e53a5b1c4f b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/12 14:21 linux-5.15.y 29e53a5b1c4f ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/11 22:53 linux-5.15.y 29e53a5b1c4f ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/11 16:27 linux-5.15.y 29e53a5b1c4f ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/08 01:29 linux-5.15.y 29e53a5b1c4f 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/07 03:10 linux-5.15.y 29e53a5b1c4f 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/10/04 06:40 linux-5.15.y 29e53a5b1c4f 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/29 13:07 linux-5.15.y 43bb85222e53 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/28 08:37 linux-5.15.y 43bb85222e53 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/23 19:34 linux-5.15.y 43bb85222e53 e667a34f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/22 17:15 linux-5.15.y 43bb85222e53 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/20 01:16 linux-5.15.y 43bb85222e53 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/19 06:06 linux-5.15.y 43bb85222e53 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/17 06:34 linux-5.15.y 43bb85222e53 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/10 03:58 linux-5.15.y de9476bb4f1b fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/02 20:58 linux-5.15.y 01879f56bdde 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/02 20:58 linux-5.15.y 01879f56bdde 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/09/01 12:06 linux-5.15.y 01879f56bdde 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/29 15:38 linux-5.15.y 01879f56bdde 3e1beec6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/29 00:53 linux-5.15.y 01879f56bdde d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/28 00:16 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/27 20:13 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/25 11:29 linux-5.15.y c79648372d02 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/08/17 20:58 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/31 12:54 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/31 12:52 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/29 22:23 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/26 21:57 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/20 16:09 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/18 16:05 linux-5.15.y c79648372d02 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/18 06:14 linux-5.15.y c79648372d02 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_read_virt_blocks
2025/07/17 16:48 linux-5.15.y 89950c454265 0d1223f1 .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
2025/08/19 06:16 linux-5.15.y c79648372d02 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/31 21:33 linux-5.15.y c79648372d02 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/31 19:21 linux-5.15.y c79648372d02 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/30 20:18 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/25 01:14 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/24 12:54 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/22 03:48 linux-5.15.y c79648372d02 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/20 02:04 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/20 00:32 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_read_virt_blocks
2025/07/19 16:58 linux-5.15.y c79648372d02 7117feec .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.