BUG: workqueue leaked lock or atomic in blk_mq_requeue_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 23a46422c561 Merge tag 'net-5.17-rc2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13a303e4700000
kernel config: https://syzkaller.appspot.com/x/.config?x=e67a4c5ed1c34c67
dashboard link: https://syzkaller.appspot.com/bug?extid=7b66771e7f5f85abc360
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
CC: [ak...@linux-foundation.org el...@google.com gli...@google.com john....@linutronix.de linux-...@vger.kernel.org pml...@suse.com rdu...@infradead.org swb...@chromium.org]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7b6677...@syzkaller.appspotmail.com

BUG: workqueue leaked lock or atomic: kworker/0:1H/0x00000000/67
last function: blk_mq_requeue_work
INFO: lockdep is turned off.
CPU: 0 PID: 67 Comm: kworker/0:1H Not tainted 5.17.0-rc1-syzkaller-00186-g23a46422c561 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Workqueue: kblockd blk_mq_requeue_work
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
process_one_work.cold+0xa2/0xba kernel/workqueue.c:2322
worker_thread+0x657/0x1110 kernel/workqueue.c:2454
kthread+0x2e9/0x3a0 kernel/kthread.c:377
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.