From: syzbot <syzbot+95fdab36405e5ffdb680@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] BUG: sleeping function called from invalid context in null_insert_page
Date: Mon, 14 Sep 2026 03:43:27 -0700 [thread overview]
Message-ID: <6aa7cfcf.f81106d8.2ab401.004b.GAE@google.com> (raw)
In-Reply-To: <6a9b44e0.a5e650b3.363816.0002.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] BUG: sleeping function called from invalid context in null_insert_page
Author: jchuang26@m.fudan.edu.cn
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 893e11787f78e43b534e252249ac3fff4d1333f8
Reported-by: syzbot+95fdab36405e5ffdb680@syzkaller.appspotmail.com
diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
index 6beb1f5b7..e22e79b02 100644
--- a/drivers/block/null_blk/main.c
+++ b/drivers/block/null_blk/main.c
@@ -1861,8 +1861,15 @@ static int null_init_global_tag_set(void)
tag_set.flags |= BLK_MQ_F_NO_SCHED_BY_DEFAULT;
if (g_shared_tag_bitmap)
tag_set.flags |= BLK_MQ_F_TAG_HCTX_SHARED;
- if (g_blocking)
- tag_set.flags |= BLK_MQ_F_BLOCKING;
+ /*
+ * Shared tag sets can be used by memory-backed devices, which may
+ * sleep in ->queue_rq() while allocating a page. The flag cannot be
+ * changed after the tag set is allocated, so always mark shared tag
+ * sets as blocking. blk-mq will then use an SRCU read lock instead
+ * of an RCU read lock around dispatch and the allocation is allowed
+ * to sleep.
+ */
+ tag_set.flags |= BLK_MQ_F_BLOCKING;
error = null_init_tag_set(&tag_set, g_poll_queues);
if (error)
prev parent reply other threads:[~2026-09-14 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 22:23 [syzbot] [block?] " syzbot
2026-09-09 21:35 ` syzbot
2026-09-14 10:22 ` Forwarded: [PATCH] " syzbot
2026-09-14 10:43 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aa7cfcf.f81106d8.2ab401.004b.GAE@google.com \
--to=syzbot+95fdab36405e5ffdb680@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®