BUG: sleeping function called from invalid context in null_process_zoned_cmd

Status: upstream: reported on 2026/08/24 15:53
Reported-by: syzbot+cee0d0645f9226471d75@syzkaller.appspotmail.com
First crash: 3d18h, last: 3d18h
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: sleeping function called from invalid context in null_process_zoned_cmd prio:low fs 5 C 4 8d13h 14d 0/29 upstream: reported C repro on 2026/08/14 09:19

Sample crash report:
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:573
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 4475, name: kworker/1:2H
3 locks held by kworker/1:2H/4475:
 #0: ffff8881449c0d38 ((wq_completion)kblockd){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000323fd00 ((work_completion)(&(&hctx->run_work)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 4475 Comm: kworker/1:2H Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: kblockd blk_mq_run_work_fn
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 ___might_sleep+0x493/0x610 kernel/sched/core.c:9658
 __mutex_lock_common+0xd3/0x2400 kernel/locking/mutex.c:573
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 null_lock_zone drivers/block/null_blk/zoned.c:46 [inline]
 null_process_zoned_cmd+0x185/0x1220 drivers/block/null_blk/zoned.c:686
 null_handle_cmd+0x362/0x990 drivers/block/null_blk/main.c:1374
 blk_mq_dispatch_rq_list+0xa06/0x1c50 block/blk-mq.c:1387
 __blk_mq_do_dispatch_sched block/blk-mq-sched.c:200 [inline]
 blk_mq_do_dispatch_sched+0xadf/0xc90 block/blk-mq-sched.c:214
 __blk_mq_sched_dispatch_requests+0x32c/0x410 block/blk-mq-sched.c:-1
 blk_mq_sched_dispatch_requests+0xf4/0x1b0 block/blk-mq-sched.c:366
 __blk_mq_run_hw_queue+0xbb/0x100 block/blk-mq.c:1512
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 4475 at kernel/locking/mutex.c:575 __mutex_lock_common+0x193b/0x2400 kernel/locking/mutex.c:575
Modules linked in:
CPU: 1 PID: 4475 Comm: kworker/1:2H Tainted: G        W         syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: kblockd blk_mq_run_work_fn
RIP: 0010:__mutex_lock_common+0x193b/0x2400 kernel/locking/mutex.c:575
Code: 00 00 83 3d de 6c c2 03 00 4c 8d b4 24 e0 00 00 00 0f 85 02 e8 ff ff 48 c7 c7 e0 1a 2b 8a 48 c7 c6 20 1b 2b 8a e8 85 85 ec ff <0f> 0b e9 e8 e7 ff ff e8 b9 a8 37 f7 e9 41 fb ff ff 0f 0b e9 63 f1
RSP: 0018:ffffc9000323f560 EFLAGS: 00010246
RAX: 840725379a5e2e00 RBX: ffff8880488c0000 RCX: ffff88802a6e0000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000323f6e8 R08: ffff8880b912795b R09: 1ffff11017224f2b
R10: dffffc0000000000 R11: ffffed1017224f2c R12: 0000000000000000
R13: dffffc0000000000 R14: ffffc9000323f640 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f49f66768b3 CR3: 000000007948f000 CR4: 00000000003526e0
Call Trace:
 <TASK>
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 null_lock_zone drivers/block/null_blk/zoned.c:46 [inline]
 null_process_zoned_cmd+0x185/0x1220 drivers/block/null_blk/zoned.c:686
 null_handle_cmd+0x362/0x990 drivers/block/null_blk/main.c:1374
 blk_mq_dispatch_rq_list+0xa06/0x1c50 block/blk-mq.c:1387
 __blk_mq_do_dispatch_sched block/blk-mq-sched.c:200 [inline]
 blk_mq_do_dispatch_sched+0xadf/0xc90 block/blk-mq-sched.c:214
 __blk_mq_sched_dispatch_requests+0x32c/0x410 block/blk-mq-sched.c:-1
 blk_mq_sched_dispatch_requests+0xf4/0x1b0 block/blk-mq-sched.c:366
 __blk_mq_run_hw_queue+0xbb/0x100 block/blk-mq.c:1512
 process_one_work+0x867/0xff0 kernel/workqueue.c:2310
 worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/24 15:52 linux-5.15.y 945fa863f02c b55bd4c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: sleeping function called from invalid context in null_process_zoned_cmd
* Struck through repros no longer work on HEAD.