possible deadlock in blkg_conf_prep

Status: upstream: reported C repro on 2026/08/15 14:47
Subsystems: cgroups block
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com
First crash: 54d, 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 2 (2) 2026/08/31 11:00
[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/5973 is trying to acquire lock:
ffffffff8efcb2a0 (fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:316 [inline]
ffffffff8efcb2a0 (fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slub.c:4636 [inline]
ffffffff8efcb2a0 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:4974 [inline]
ffffffff8efcb2a0 (fs_reclaim){+.+.}-{0:0}, at: kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:5010

but task is already holding lock:
ffff888029af3270 (&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:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x1a4/0x1bd0 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)#65){++++}-{0:0}:
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       blk_alloc_queue+0x610/0x790 block/blk-core.c:504
       __blk_alloc_disk+0xa0/0x170 block/genhd.c:1527
       zram_add+0x1bf/0x5d0 drivers/block/zram/zram_drv.c:3096
       zram_init+0x11c/0x160 drivers/block/zram/zram_drv.c:3296
       do_one_initcall+0x11c/0x6f0 init/main.c:1362
       do_initcall_level init/main.c:1424 [inline]
       do_initcalls init/main.c:1440 [inline]
       do_basic_setup init/main.c:1460 [inline]
       kernel_init_freeable+0x6ea/0x7b0 init/main.c:1675
       kernel_init+0x21/0x1e0 init/main.c:1565
       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:3209
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
       lock_acquire kernel/locking/lockdep.c:5942 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
       __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:316 [inline]
       slab_pre_alloc_hook mm/slub.c:4636 [inline]
       slab_alloc_node mm/slub.c:4974 [inline]
       kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:5010
       __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)#65 --> &q->blkcg_mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

locks held by syz.1.18/5973: 5, last CPU#2:
 #0: ffff888035b50460 (sb_writers#11){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
 #1: ffff8880567ea080 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x2c2/0x5f0 fs/kernfs/file.c:336
 #2: ffff88803df7ed28 (kn->active#66){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:73 [inline]
 #2: ffff88803df7ed28 (kn->active#66){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x332/0x5f0 fs/kernfs/file.c:337
 #3: ffff888029af30f0 (&q->rq_qos_mutex){+.+.}-{4:4}, at: blkg_conf_open_bdev+0x253/0x410 block/blk-cgroup.c:806
 #4: ffff888029af3270 (&q->blkcg_mutex){+.+.}-{4:4}, at: blkg_conf_prep+0xbc/0xf10 block/blk-cgroup.c:849

stack backtrace:
CPU: 2 UID: 0 PID: 5973 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:2087
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2219
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
 lock_acquire kernel/locking/lockdep.c:5942 [inline]
 lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
 __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:316 [inline]
 slab_pre_alloc_hook mm/slub.c:4636 [inline]
 slab_alloc_node mm/slub.c:4974 [inline]
 kmem_cache_alloc_noprof+0x63/0x6a0 mm/slub.c:5010
 __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:0x7f52cbf9e159
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:00007ffc6fd5fea8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f52cc225fa0 RCX: 00007f52cbf9e159
RDX: 0000000000000008 RSI: 0000200000000480 RDI: 0000000000000003
RBP: 00007f52cc03506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f52cc225fac R14: 00007f52cc225fa0 R15: 00007f52cc225fa0
 </TASK>

Crashes (1325):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/04 18:57 upstream 6addb4f38557 57bbd979 .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/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/10/04 18:19 upstream 6addb4f38557 57bbd979 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 17:08 upstream 6addb4f38557 57bbd979 .config console log report syz / log [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/09/05 07:24 upstream 654ae5d73c05 4f7b22a0 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/04 15:14 upstream 6addb4f38557 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/03 23:41 upstream a74306e2e676 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/10/03 22:25 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/10/03 19:50 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in blkg_conf_prep
2026/10/03 17:38 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in blkg_conf_prep
2026/10/03 09:32 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/03 05:14 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/10/03 02:14 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/02 23:27 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/10/02 19:23 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in blkg_conf_prep
2026/10/02 18:01 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/02 11:12 upstream d24e8ac715de 6d32eb1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/10/02 02:31 upstream d24e8ac715de 6d32eb1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/01 18:17 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in blkg_conf_prep
2026/10/01 14:50 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in blkg_conf_prep
2026/09/21 11:02 upstream 93f51579e7df 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in blkg_conf_prep
2026/10/04 07:38 upstream a74306e2e676 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/10/04 03:00 upstream a74306e2e676 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/10/02 16:11 upstream ce1e0223d8ad 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/10/01 23:33 upstream d24e8ac715de 6d32eb1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/10/01 06:44 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in blkg_conf_prep
2026/10/04 16:27 upstream 6addb4f38557 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 12:10 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 09:43 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 05:49 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 04:43 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/03 20:27 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/03 07:38 upstream 3b7cab693ba2 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/03 06:22 upstream 3b7cab693ba2 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/03 00:29 upstream 3b7cab693ba2 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/02 20:47 upstream 3b7cab693ba2 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/02 17:15 upstream ce1e0223d8ad 1065c8fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/02 08:15 upstream ce1e0223d8ad 1065c8fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/02 04:23 upstream d24e8ac715de 6d32eb1f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/01 20:38 upstream d24e8ac715de 6d32eb1f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/01 10:35 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/01 10:02 upstream 551c722f4080 38f7f0d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in blkg_conf_prep
2026/10/01 07:47 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in blkg_conf_prep
2026/10/04 18:10 upstream 6addb4f38557 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/04 13:19 upstream 6addb4f38557 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/04 00:56 upstream a74306e2e676 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/03 16:04 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/03 14:33 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/03 13:19 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/03 11:00 upstream e767a4ea70a3 57bbd979 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/02 15:07 upstream ce1e0223d8ad 1065c8fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/02 13:08 upstream ce1e0223d8ad 1065c8fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/01 11:35 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/10/01 05:33 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in blkg_conf_prep
2026/09/30 09:25 linux-next 6474fa070f2b 7808aef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in blkg_conf_prep
2026/09/29 03:09 linux-next 6375e61c01e9 7bf4ea23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce 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
2026/10/02 09:42 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7ce5295296b5 6d32eb1f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in blkg_conf_prep
* Struck through repros no longer work on HEAD.