From: Hillf Danton <hdanton@sina.com>
To: Sam Sun <samsun1006219@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
syzkaller-bugs@googlegroups.com, xrivendell7@gmail.com
Subject: Re: [Linux kernel bug] INFO: task hung in blk_mq_get_tag
Date: Tue, 14 May 2024 06:54:09 +0800 [thread overview]
Message-ID: <20240513225409.3025-1-hdanton@sina.com> (raw)
In-Reply-To: <CAEkJfYPxWBfEnuKeCGEsscVTYy8MrNxCJwdbxS=c2-B0H+HfTA@mail.gmail.com>
On Mon, 13 May 2024 20:57:44 +0800 Sam Sun <samsun1006219@gmail.com>
>
> I am happy to help testing patches. As
Thanks.
> for repro, I have a C repro available, but it is too long so that I
> attached it to the first email. Should I just paste repro with bug
> report?
Yes.
> I applied this patch and tried using the C repro, but it still crashed
> with the same task hang kernel dump log.
Oh low-hanging pear is sour, and try again seeing if there is missing
wakeup due to wake batch.
--- x/lib/sbitmap.c
+++ y/lib/sbitmap.c
@@ -579,6 +579,8 @@ void sbitmap_queue_wake_up(struct sbitma
unsigned int wake_batch = READ_ONCE(sbq->wake_batch);
unsigned int wakeups;
+ __sbitmap_queue_wake_up(sbq, nr);
+
if (!atomic_read(&sbq->ws_active))
return;
--
next prev parent reply other threads:[~2024-05-13 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 2:38 [Linux kernel bug] INFO: task hung in blk_mq_get_tag Sam Sun
2024-05-13 10:54 ` Hillf Danton
2024-05-13 12:57 ` Sam Sun
2024-05-13 14:16 ` Tetsuo Handa
2024-05-13 14:49 ` Sam Sun
2024-05-13 22:54 ` Hillf Danton [this message]
2024-05-14 2:05 ` Sam Sun
2024-05-14 7:39 ` Tetsuo Handa
2024-05-14 10:37 ` Hillf Danton
2024-05-14 12:07 ` Sam Sun
2024-05-14 14:45 ` Tetsuo Handa
2024-05-15 12:46 ` Sam Sun
2024-05-15 13:12 ` Tetsuo Handa
2024-05-14 22:41 ` Hillf Danton
2024-05-15 10:13 ` Tetsuo Handa
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=20240513225409.3025-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=samsun1006219@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@gmail.com \
/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