syzbot


possible deadlock in deactivate_super (2)

Status: upstream: reported C repro on 2025/02/02 14:09
Subsystems: ocfs2
[Documentation on labels]
Reported-by: syzbot+180dd013ba371eabc162@syzkaller.appspotmail.com
First crash: 64d, last: 1h58m
Cause bisection: the cause commit could be any of (bisect log):
  309a43165077 rcu/kvfree: Use consistent krcp when growing kfree_rcu() page cache
  021a5ff84743 rcu/kvfree: Do not run a page work if a cache is disabled
  1e237994d9c9 rcu/kvfree: Invoke debug_rcu_bhead_unqueue() after checking bnode->gp_snap
  60888b77a06e rcu/kvfree: Make fill page cache start from krcp->nr_bkv_objs
  f32276a37652 rcu/kvfree: Add debug check for GP complete for kfree_rcu_cpu list
  6b706e5603c4 rcu/kvfree: Make drain_page_cache() take early return if cache is disabled
  cdfa0f6fa6b7 rcu/kvfree: Add debug to check grace periods
  2e31da752c6d Merge branches 'doc.2023.05.10a', 'fixes.2023.05.11a', 'kvfree.2023.05.10a', 'nocb.2023.05.11a', 'rcu-tasks.2023.05.10a', 'torture.2023.05.15a' and 'rcu-urgent.2023.06.06a' into HEAD
  7e3f926bf453 rcu/kvfree: Eliminate k[v]free_rcu() single argument macro
  af96134dc856 Merge tag 'rcu.2023.06.22a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly ocfs2 report (Mar 2025) 0 (1) 2025/03/31 13:08
[syzbot] Monthly ocfs2 report (Feb 2025) 0 (1) 2025/02/26 12:08
[syzbot] [ocfs2?] possible deadlock in deactivate_super (2) 0 (1) 2025/02/02 14:09
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in deactivate_super origin:upstream C 572 10h25m 63d 0/3 upstream: reported C repro on 2025/01/29 18:51
upstream possible deadlock in deactivate_super ext4 C unreliable 9 1079d 1099d 0/28 closed as dup on 2022/03/30 22:17
linux-6.1 possible deadlock in deactivate_super origin:upstream C 1148 11h46m 63d 0/3 upstream: reported C repro on 2025/01/29 20:18

Sample crash report:
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
6.14.0-syzkaller-12886-ga1b5bd45d4ee #0 Not tainted
------------------------------------------------------
syz-executor299/5829 is trying to acquire lock:
ffff888028b9c148 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0xb1/0x170 kernel/workqueue.c:3907

but task is already holding lock:
ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline]
ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&type->s_umount_key#45){++++}-{4:4}:
       lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
       down_read+0xb3/0xa50 kernel/locking/rwsem.c:1524
       ocfs2_finish_quota_recovery+0x15e/0x2310 fs/ocfs2/quota_local.c:603
       ocfs2_complete_recovery+0x1977/0x2580 fs/ocfs2/journal.c:1357
       process_one_work kernel/workqueue.c:3238 [inline]
       process_scheduled_works+0xac3/0x18e0 kernel/workqueue.c:3319
       worker_thread+0x870/0xd50 kernel/workqueue.c:3400
       kthread+0x7b7/0x940 kernel/kthread.c:464
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #1 ((work_completion)(&journal->j_recovery_work)){+.+.}-{0:0}:
       lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
       process_one_work kernel/workqueue.c:3214 [inline]
       process_scheduled_works+0x9e9/0x18e0 kernel/workqueue.c:3319
       worker_thread+0x870/0xd50 kernel/workqueue.c:3400
       kthread+0x7b7/0x940 kernel/kthread.c:464
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 ((wq_completion)ocfs2_wq){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909
       __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235
       lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
       touch_wq_lockdep_map+0xc7/0x170 kernel/workqueue.c:3907
       __flush_workqueue+0x14c/0x1280 kernel/workqueue.c:3949
       ocfs2_shutdown_local_alloc+0x10b/0xab0 fs/ocfs2/localalloc.c:380
       ocfs2_dismount_volume+0x204/0x910 fs/ocfs2/super.c:1822
       generic_shutdown_super+0x139/0x2d0 fs/super.c:642
       kill_block_super+0x44/0x90 fs/super.c:1710
       deactivate_locked_super+0xc4/0x130 fs/super.c:473
       cleanup_mnt+0x422/0x4c0 fs/namespace.c:1435
       task_work_run+0x251/0x310 kernel/task_work.c:227
       exit_task_work include/linux/task_work.h:40 [inline]
       do_exit+0xa11/0x27f0 kernel/exit.c:953
       do_group_exit+0x207/0x2c0 kernel/exit.c:1102
       __do_sys_exit_group kernel/exit.c:1113 [inline]
       __se_sys_exit_group kernel/exit.c:1111 [inline]
       __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1111
       x64_sys_call+0x26c3/0x26d0 arch/x86/include/generated/asm/syscalls_64.h:232
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xf3/0x230 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:
  (wq_completion)ocfs2_wq --> (work_completion)(&journal->j_recovery_work) --> &type->s_umount_key#45

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&type->s_umount_key#45);
                               lock((work_completion)(&journal->j_recovery_work));
                               lock(&type->s_umount_key#45);
  lock((wq_completion)ocfs2_wq);

 *** DEADLOCK ***

1 lock held by syz-executor299/5829:
 #0: ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline]
 #0: ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
 #0: ffff888035c020e0 (&type->s_umount_key#45){++++}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505

stack backtrace:
CPU: 1 UID: 0 PID: 5829 Comm: syz-executor299 Not tainted 6.14.0-syzkaller-12886-ga1b5bd45d4ee #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2079
 check_noncircular+0x142/0x160 kernel/locking/lockdep.c:2211
 check_prev_add kernel/locking/lockdep.c:3166 [inline]
 check_prevs_add kernel/locking/lockdep.c:3285 [inline]
 validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909
 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235
 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
 touch_wq_lockdep_map+0xc7/0x170 kernel/workqueue.c:3907
 __flush_workqueue+0x14c/0x1280 kernel/workqueue.c:3949
 ocfs2_shutdown_local_alloc+0x10b/0xab0 fs/ocfs2/localalloc.c:380
 ocfs2_dismount_volume+0x204/0x910 fs/ocfs2/super.c:1822
 generic_shutdown_super+0x139/0x2d0 fs/super.c:642
 kill_block_super+0x44/0x90 fs/super.c:1710
 deactivate_locked_super+0xc4/0x130 fs/super.c:473
 cleanup_mnt+0x422/0x4c0 fs/namespace.c:1435
 task_work_run+0x251/0x310 kernel/task_work.c:227
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0xa11/0x27f0 kernel/exit.c:953
 do_group_exit+0x207/0x2c0 kernel/exit.c:1102
 __do_sys_exit_group kernel/exit.c:1113 [inline]
 __se_sys_exit_group kernel/exit.c:1111 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1111
 x64_sys_call+0x26c3/0x26d0 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe7e5864c09
Code: Unable to access opcode bytes at 0x7fe7e5864bdf.
RSP: 002b:00007ffd5003f078 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fe7e5864c09
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fe7e58e52b0 R08: ffffffffffffffb8 R09: 0000000000004701
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe7e58e52b0
R13: 0000000000000000 R14: 00007fe7e58e6020 R15: 00007fe7e5833130
 </TASK>
ocfs2: Unmounting device (7,0) on (node local)

Crashes (6544):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/03 09:31 upstream a1b5bd45d4ee 996a9618 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 16:24 upstream acc4d5ff0b61 c799dfdd .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/18 23:05 upstream 76b6905c11fd 22a6c2b1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/18 21:35 upstream 76b6905c11fd 22a6c2b1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/13 14:21 upstream b7f94fcf5546 44be8b44 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/12 01:50 upstream 0b46b049d6ec ee70e6db .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/10 12:22 upstream 80e54e84911a 163f510d .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/09 07:13 upstream b7c90e3e717a 163f510d .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/08 01:25 upstream 00a7d39898c8 7e3bd60d .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/06 23:43 upstream 848e07631744 831e3629 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/05 19:48 upstream bb2281fb05e5 60f5d8d9 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/04 15:55 upstream 99fa936e8e4f c3901742 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/01 20:19 upstream 03d38806a902 c3901742 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/28 17:20 upstream 76544811c850 67cf5345 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/27 00:26 upstream 5394eea10651 6a8fcbc4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/25 02:42 upstream d082ecbc71e9 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/23 06:03 upstream 5cf80612d3f7 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/23 04:30 upstream 5cf80612d3f7 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-upstream-kasan-gce-root possible deadlock in deactivate_super
2025/02/20 23:00 upstream e9a8cac0bf89 0808a665 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/19 00:33 upstream 6537cfb395f3 9a14138f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/15 12:22 upstream 78a632a2086c 40a34ec9 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/14 11:29 upstream 68763b29e0a6 d9a046cf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/12 20:55 upstream 09fbf3d50205 b27c2402 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/11 17:03 upstream febbc555cf0f f2baddf5 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/09 09:01 upstream 9946eaf552b1 ef44b750 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/08 05:54 upstream 7ee983c850b4 ef44b750 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/06 19:49 upstream 92514ef226f5 8002dd28 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/04 07:00 upstream 0de63bb7d919 8f267cef .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/03 04:21 upstream 69b8923f5003 568559e4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/01 22:31 upstream 69b8923f5003 568559e4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/01 16:35 upstream 69b8923f5003 aa47157c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/01 14:09 upstream 69b8923f5003 aa47157c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/01 13:55 upstream 69b8923f5003 aa47157c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/02/01 13:22 upstream 69b8923f5003 aa47157c .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/12 01:15 upstream 0b46b049d6ec ee70e6db .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/03/04 13:53 upstream 99fa936e8e4f c3901742 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/26 20:16 upstream ac9c34d1e45a 6a8fcbc4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/14 06:12 upstream ab68d7eb7b1a d9a046cf .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/05 13:49 upstream 5c8c229261f1 5896748e .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/04 06:38 upstream 0de63bb7d919 8f267cef .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/03 03:18 upstream 69e858e0b8b2 568559e4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/02/20 21:03 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e6747d19291c 50668798 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-upstream-gce-arm64 possible deadlock in deactivate_super
2025/01/29 14:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 865ef71e .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in deactivate_super
2025/04/03 15:31 upstream a1b5bd45d4ee 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 12:36 upstream a1b5bd45d4ee 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 10:10 upstream a1b5bd45d4ee 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 09:07 upstream a1b5bd45d4ee 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 06:58 upstream a1b5bd45d4ee 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 04:22 upstream 92b71befc349 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/03 02:31 upstream 92b71befc349 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 22:49 upstream 92b71befc349 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 21:12 upstream 92b71befc349 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 19:14 upstream 92b71befc349 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 17:45 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 15:29 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 12:07 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 06:08 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 05:02 upstream acc4d5ff0b61 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 05:02 upstream acc4d5ff0b61 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 04:02 upstream acc4d5ff0b61 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 02:57 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/02 00:58 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 23:45 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 21:51 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 19:57 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 17:28 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 15:54 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 14:45 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 14:41 upstream 08733088b566 b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 12:50 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 08:21 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 07:05 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 02:58 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 01:57 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 01:54 upstream 1e7857b28020 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/04/01 00:21 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 23:07 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 23:06 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 21:18 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 19:43 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 16:19 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 12:28 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/31 12:28 upstream 4e82c87058f4 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in deactivate_super
2025/03/23 19:48 upstream 586de92313fc 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in deactivate_super
2025/03/21 03:06 upstream 5fc319360819 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in deactivate_super
2025/04/03 01:07 upstream acc4d5ff0b61 b0cc4801 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in deactivate_super
2025/04/02 23:57 linux-next fefb886b1344 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in deactivate_super
2025/04/01 06:02 linux-next 7b7d0894c661 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in deactivate_super
2025/04/01 05:59 linux-next 7b7d0894c661 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in deactivate_super
2025/03/31 20:00 linux-next 405e2241def8 36d76a97 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in deactivate_super
2025/03/23 18:21 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in deactivate_super
* Struck through repros no longer work on HEAD.