[moderation] [block?] WARNING: lock held when returning to user space in blk_mq_freeze_queue_nomemsave

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6addb4f38557 Merge tag 'edac_urgent_for_v7.3_rc6' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=116617f5580000
kernel config: https://syzkaller.appspot.com/x/.config?x=929e4854a828f434
dashboard link: https://syzkaller.appspot.com/bug?extid=96a17b2abf8665f6903b
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-6addb4f3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16e934f39bde/vmlinux-6addb4f3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/80bd6fc0adf1/bzImage-6addb4f3.xz

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

================================================
WARNING: lock held when returning to user space!
syzkaller #0 Not tainted
------------------------------------------------
syz.3.475/8501 is leaving the kernel with locks still held!
locks held by syz.3.475/8501: 2, last CPU#0:
#0: ffff88803aec1c50 (&q->q_usage_counter(io)#223){++++}-{0:0}, at: blk_mq_freeze_queue_nomemsave+0x15/0x20 block/blk-mq.c:206
#1: ffff88803aec1c88 (&q->q_usage_counter(queue)#207){+.+.}-{0:0}, at: blk_mq_freeze_queue_nomemsave+0x15/0x20 block/blk-mq.c:206


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup