syzbot
possible deadlock in blkg_conf_prep
Status:
upstream: reported on 2026/08/15 14:47
Subsystems:
block
cgroups
Labels:
prio:high
[Documentation on labels]
Reported-by: syzbot+144a1c0e22e53a08ef5a@syzkaller.appspotmail.com
First crash: 6d09h, last: 2h57m
▶
▼
Last patch testing requests (1)
| Created |
Duration |
User |
Patch |
Repo |
Result |
| 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.508/7108 is trying to acquire lock:
ffffffff8f088c20 (fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:316 [inline]
ffffffff8f088c20 (fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slub.c:4636 [inline]
ffffffff8f088c20 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:4974 [inline]
ffffffff8f088c20 (fs_reclaim){+.+.}-{0:0}, at: kmem_cache_alloc_noprof+0x5f/0x600 mm/slub.c:5010
but task is already holding lock:
ffff888026196100 (&q->blkcg_mutex){+.+.}-{4:4}, at: blkg_conf_prep+0xa3/0xd80 block/blk-cgroup.c:846
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&q->blkcg_mutex){+.+.}-{4:4}:
__mutex_lock_common kernel/locking/mutex.c:646 [inline]
__mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
blkcg_activate_policy+0x1cb/0x8e0 block/blk-cgroup.c:1595
blk_throtl_init+0x2f7/0x420 block/blk-throttle.c:1339
tg_set_conf+0x1db/0x4e0 block/blk-throttle.c:1368
cgroup_file_write+0x331/0x8f0 kernel/cgroup/cgroup.c:4412
kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x612/0xba0 fs/read_write.c:687
ksys_write+0x150/0x270 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
-> #1 (&q->q_usage_counter(io)#2){++++}-{0:0}:
blk_alloc_queue+0x544/0x690 block/blk-core.c:504
__blk_alloc_disk+0xe3/0x1d0 block/genhd.c:1519
brd_alloc+0x436/0x7c0 drivers/block/brd.c:327
brd_init+0xc1/0x120 drivers/block/brd.c:420
do_one_initcall+0x250/0x870 init/main.c:1359
do_initcall_level+0x10a/0x1a0 init/main.c:1421
do_initcalls+0x59/0xa0 init/main.c:1437
kernel_init_freeable+0x29d/0x3e0 init/main.c:1672
kernel_init+0x22/0x1d0 init/main.c:1562
ret_from_fork+0x514/0xb70 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 kernel/locking/lockdep.c:3181 [inline]
check_prevs_add kernel/locking/lockdep.c:3300 [inline]
validate_chain kernel/locking/lockdep.c:3924 [inline]
__lock_acquire+0x15ff/0x2e50 kernel/locking/lockdep.c:5254
lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
__fs_reclaim_acquire mm/page_alloc.c:4375 [inline]
fs_reclaim_acquire+0x71/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+0x5f/0x600 mm/slub.c:5010
__radix_tree_preload+0x2df/0x870 lib/radix-tree.c:338
blkg_conf_prep+0x621/0xd80 block/blk-cgroup.c:882
tg_set_conf+0x20b/0x4e0 block/blk-throttle.c:1373
cgroup_file_write+0x331/0x8f0 kernel/cgroup/cgroup.c:4412
kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x612/0xba0 fs/read_write.c:687
ksys_write+0x150/0x270 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 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)#2 --> &q->blkcg_mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&q->blkcg_mutex);
lock(&q->q_usage_counter(io)#2);
lock(&q->blkcg_mutex);
lock(fs_reclaim);
*** DEADLOCK ***
locks held by syz.1.508/7108: 6, last CPU#1:
#0: ffff888029c549b0 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x246/0x320 fs/file.c:1259
#1: ffff8880253b2460 (sb_writers#10){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2753 [inline]
#1: ffff8880253b2460 (sb_writers#10){.+.+}-{0:0}, at: vfs_write+0x22b/0xba0 fs/read_write.c:683
#2: ffff88807a071480 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1d8/0x540 fs/kernfs/file.c:336
#3: ffff8880339fbd28 (kn->active#70){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:73 [inline]
#3: ffff8880339fbd28 (kn->active#70){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x22b/0x540 fs/kernfs/file.c:337
#4: ffff888026195f80 (&q->rq_qos_mutex){+.+.}-{4:4}, at: blkg_conf_open_bdev+0x2a8/0x3c0 block/blk-cgroup.c:803
#5: ffff888026196100 (&q->blkcg_mutex){+.+.}-{4:4}, at: blkg_conf_prep+0xa3/0xd80 block/blk-cgroup.c:846
stack backtrace:
CPU: 1 UID: 0 PID: 7108 Comm: syz.1.508 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2059
check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2191
check_prev_add kernel/locking/lockdep.c:3181 [inline]
check_prevs_add kernel/locking/lockdep.c:3300 [inline]
validate_chain kernel/locking/lockdep.c:3924 [inline]
__lock_acquire+0x15ff/0x2e50 kernel/locking/lockdep.c:5254
lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908
__fs_reclaim_acquire mm/page_alloc.c:4375 [inline]
fs_reclaim_acquire+0x71/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+0x5f/0x600 mm/slub.c:5010
__radix_tree_preload+0x2df/0x870 lib/radix-tree.c:338
blkg_conf_prep+0x621/0xd80 block/blk-cgroup.c:882
tg_set_conf+0x20b/0x4e0 block/blk-throttle.c:1373
cgroup_file_write+0x331/0x8f0 kernel/cgroup/cgroup.c:4412
kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x612/0xba0 fs/read_write.c:687
ksys_write+0x150/0x270 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2b34b9e0d9
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:00007f2b35b40028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f2b34e25fa0 RCX: 00007f2b34b9e0d9
RDX: 000000000000006a RSI: 00002000000000c0 RDI: 0000000000000005
RBP: 00007f2b34c35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2b34e26038 R14: 00007f2b34e25fa0 R15: 00007ffff2626318
</TASK>
* Struck through repros no longer work on HEAD.