possible deadlock in blkg_conf_prep

Status: upstream: reported C repro on 2026/08/15 14:47
Subsystems: block cgroups
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com
First crash: 19d, last: now
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
c98a1e4a repro-c Reproduced: ✅ possible deadlock in blkg_conf_prep 2026/08/16 13:35 2026/08/16 18:10 2026/08/16 20:07 746171ee
6aa9899d assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ✅ VMHostTrigger: ❌ possible deadlock in blkg_conf_prep 2026/08/13 00:00 2026/08/13 00:00 2026/08/13 00:58 a56bc0a5
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] blk-cgroup: use GFP_NOIO for radix tree preload in blkg_conf_prep 1 (1) 2026/08/31 05:57
[syzbot] [block?] [cgroups?] possible deadlock in blkg_conf_prep 0 (3) 2026/08/29 00:33
Last patch testing requests (4)
Created Duration User Patch Repo Result
2026/08/31 05:20 21m tao1.yu@intel.com https://github.com/yutao-intel/linux.git fix-linux-next-block-blk-cgroups no crash job log log
2026/08/31 03:26 22m tao1.yu@intel.com https://github.com/yutao-intel/linux.git fix-linux-next-block-blk-cgroups job log log
2026/08/31 03:15 0m tao1.yu@intel.com patch upstream error job log
2026/08/17 08:59 14m nogikh@google.com upstream no crash job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.18/6027 is trying to acquire lock:
ffffffff8efc6c00
 (
fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:314 [inline]
fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slub.c:4539 [inline]
fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:4899 [inline]
fs_reclaim){+.+.}-{0:0}, at: kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:4933

but task is already holding lock:
ffff888028683bc0 (&q->blkcg_mutex){+.+.}-{4:4}, at: blkg_conf_prep+0xbc/0xf10 block/blk-cgroup.c:849

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&q->blkcg_mutex){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x1a4/0x1bc0 kernel/locking/mutex.c:821
       blkcg_activate_policy+0x34f/0xbf0 block/blk-cgroup.c:1608
       blk_throtl_init+0x39a/0x5b0 block/blk-throttle.c:1339
       tg_set_conf.isra.0+0x252/0x500 block/blk-throttle.c:1368
       cgroup_file_write+0x1e6/0x8a0 kernel/cgroup/cgroup.c:4412
       kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x6af/0x1050 fs/read_write.c:687
       ksys_write+0x12a/0x250 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&q->q_usage_counter(io)#17){++++}-{0:0}:
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       blk_alloc_queue+0x610/0x790 block/blk-core.c:504
       blk_mq_alloc_queue+0x174/0x290 block/blk-mq.c:4420
       __blk_mq_alloc_disk+0x29/0x120 block/blk-mq.c:4467
       loop_add+0x498/0xb60 drivers/block/loop.c:2071
       loop_init+0x1d3/0x200 drivers/block/loop.c:2310
       do_one_initcall+0x11c/0x6f0 init/main.c:1353
       do_initcall_level init/main.c:1415 [inline]
       do_initcalls init/main.c:1431 [inline]
       do_basic_setup init/main.c:1451 [inline]
       kernel_init_freeable+0x6ea/0x7b0 init/main.c:1666
       kernel_init+0x21/0x1e0 init/main.c:1556
       ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 (fs_reclaim){+.+.}-{0:0}:
       check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
       check_prevs_add kernel/locking/lockdep.c:3300 [inline]
       validate_chain kernel/locking/lockdep.c:3924 [inline]
       __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5253
       lock_acquire kernel/locking/lockdep.c:5886 [inline]
       lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
       __fs_reclaim_acquire mm/page_alloc.c:4375 [inline]
       fs_reclaim_acquire+0xc4/0x100 mm/page_alloc.c:4389
       might_alloc include/linux/sched/mm.h:314 [inline]
       slab_pre_alloc_hook mm/slub.c:4539 [inline]
       slab_alloc_node mm/slub.c:4899 [inline]
       kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:4933
       __radix_tree_preload+0x333/0x820 lib/radix-tree.c:338
       blkg_conf_prep+0x489/0xf10 block/blk-cgroup.c:885
       tg_set_conf.isra.0+0x1ed/0x500 block/blk-throttle.c:1373
       cgroup_file_write+0x1e6/0x8a0 kernel/cgroup/cgroup.c:4412
       kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x6af/0x1050 fs/read_write.c:687
       ksys_write+0x12a/0x250 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  fs_reclaim --> &q->q_usage_counter(io)#17 --> &q->blkcg_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&q->blkcg_mutex);
                               lock(&q->q_usage_counter(io)#17);
                               lock(&q->blkcg_mutex);
  lock(fs_reclaim);

 *** DEADLOCK ***

locks held by syz.1.18/6027: 6, last CPU#3:
 #0: ffff888035cc8b70 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x2aa/0x380 fs/file.c:1259
 #1: ffff8880372a4460 (sb_writers#11){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
 #2: ffff888037174c80 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x2c2/0x5f0 fs/kernfs/file.c:336
 #3: ffff8880534200f8 (kn->active#66){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:73 [inline]
 #3: ffff8880534200f8 (kn->active#66){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x332/0x5f0 fs/kernfs/file.c:337
 #4: ffff888028683a40 (&q->rq_qos_mutex){+.+.}-{4:4}, at: blkg_conf_open_bdev+0x253/0x410 block/blk-cgroup.c:806
 #5: ffff888028683bc0 (&q->blkcg_mutex){+.+.}-{4:4}, at: blkg_conf_prep+0xbc/0xf10 block/blk-cgroup.c:849

stack backtrace:
CPU: 3 UID: 0 PID: 6027 Comm: syz.1.18 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2059
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2191
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
 check_prevs_add kernel/locking/lockdep.c:3300 [inline]
 validate_chain kernel/locking/lockdep.c:3924 [inline]
 __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5253
 lock_acquire kernel/locking/lockdep.c:5886 [inline]
 lock_acquire+0x1b9/0x370 kernel/locking/lockdep.c:5843
 __fs_reclaim_acquire mm/page_alloc.c:4375 [inline]
 fs_reclaim_acquire+0xc4/0x100 mm/page_alloc.c:4389
 might_alloc include/linux/sched/mm.h:314 [inline]
 slab_pre_alloc_hook mm/slub.c:4539 [inline]
 slab_alloc_node mm/slub.c:4899 [inline]
 kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:4933
 __radix_tree_preload+0x333/0x820 lib/radix-tree.c:338
 blkg_conf_prep+0x489/0xf10 block/blk-cgroup.c:885
 tg_set_conf.isra.0+0x1ed/0x500 block/blk-throttle.c:1373
 cgroup_file_write+0x1e6/0x8a0 kernel/cgroup/cgroup.c:4412
 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6af/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7b6519e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7b66080028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7b65425fa0 RCX: 00007f7b6519e159
RDX: 000000000000006a RSI: 00002000000000c0 RDI: 0000000000000005
RBP: 00007f7b65235024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7b65426038 R14: 00007f7b65425fa0 R15: 00007ffc8680c158
 </TASK>

Crashes (300):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/29 00:33 upstream 818bebeb63dd 2f52988a .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/25 16:52 upstream 818bebeb63dd a9a1fc32 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/21 10:29 upstream 818bebeb63dd 1e72964b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/21 09:19 upstream 818bebeb63dd 1e72964b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/30 22:43 upstream a23cbb05744b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blkg_conf_prep
2026/08/30 19:15 upstream a23cbb05744b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/30 16:12 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/30 15:11 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/08/30 13:20 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blkg_conf_prep
2026/08/29 23:09 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/08/29 21:22 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/08/29 10:38 upstream cf72cbb39da8 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blkg_conf_prep
2026/08/28 02:37 upstream 18fbf5151d2c e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/08/27 22:00 upstream 73e3f0710014 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/27 19:03 upstream 73e3f0710014 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/27 16:22 upstream 73e3f0710014 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/27 12:43 upstream 73e3f0710014 a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/08/24 03:51 upstream b6b019a1d9b9 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in blkg_conf_prep
2026/08/23 14:41 upstream 2709dd5ae32f 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blkg_conf_prep
2026/08/30 09:20 upstream 08dbfad3f504 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/08/29 07:28 upstream cf72cbb39da8 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/08/27 11:24 upstream 73e3f0710014 a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/08/31 07:54 upstream cee9395acd80 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/31 04:05 upstream a23cbb05744b 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/31 00:27 upstream a23cbb05744b 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/30 13:26 upstream 08dbfad3f504 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/30 11:10 upstream 08dbfad3f504 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/30 08:16 upstream 08dbfad3f504 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/30 06:23 upstream 08dbfad3f504 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 18:50 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 17:29 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 15:08 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 13:04 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 11:54 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 09:33 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/29 08:03 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 23:11 upstream 818bebeb63dd 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 20:05 upstream 818bebeb63dd 41d151d4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 17:41 upstream 818bebeb63dd 41d151d4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 12:38 upstream 818bebeb63dd 41d151d4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 11:25 upstream 818bebeb63dd 41d151d4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 08:45 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 06:11 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 05:11 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 04:05 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 03:52 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/28 01:19 upstream 818bebeb63dd e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/27 14:20 upstream 818bebeb63dd c53a1b9c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/27 09:34 upstream 818bebeb63dd c53a1b9c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/27 04:50 upstream 818bebeb63dd a2b77b9e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/08/31 01:45 upstream a23cbb05744b 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/30 03:28 upstream 08dbfad3f504 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/29 22:25 upstream cf72cbb39da8 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/29 05:30 upstream 548e7bcd0c54 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/29 02:00 upstream 548e7bcd0c54 2f52988a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/27 23:44 upstream 18fbf5151d2c e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/27 20:47 upstream 18fbf5151d2c e2fa417d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/27 07:28 upstream 73e3f0710014 a2b77b9e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/27 02:48 upstream 73e3f0710014 a2b77b9e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/08/28 16:24 linux-next 3d83758432b5 bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blkg_conf_prep
2026/08/28 15:58 linux-next 3d83758432b5 bcbc8ceb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blkg_conf_prep
2026/08/27 17:40 linux-next 3d83758432b5 e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in blkg_conf_prep
2026/08/21 00:42 linux-next 7079a12d7506 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blkg_conf_prep
2026/08/11 14:40 linux-next 3d08ff75a47a 37a258dd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blkg_conf_prep
* Struck through repros no longer work on HEAD.