From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Sam Sun <samsun1006219@gmail.com>, Hillf Danton <hdanton@sina.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk, 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 16:39:32 +0900 [thread overview]
Message-ID: <21d52c65-4f18-46a2-be68-ff8487103e82@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CAEkJfYMhv8AxxHSVdPT9bCX1cJZXw39+bMFh=2N9uNOB4Hcr=w@mail.gmail.com>
On 2024/05/14 11:05, Sam Sun wrote:
> Pointed out by Tetsuo, this kernel panic might be caused by sending
> NMI between cpus. As dump log shows:
You can do
# echo 0 > /proc/sys/kernel/hung_task_all_cpu_backtrace
before starting the reproducer in order to disable
trigger_all_cpu_backtrace() from hung task.
If trigger_all_cpu_backtrace() from hung task can reproduce
the kernel panic, I think that trigger_all_cpu_backtrace() from
SysRq-l should be as well able to reproduce the kernel panic.
That is, you can build with CONFIG_MAGIC_SYSRQ=y and try
# echo l > /proc/sysrq-trigger
for bisecting and reporting as a separate bug.
next prev parent reply other threads:[~2024-05-14 7:39 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
2024-05-14 2:05 ` Sam Sun
2024-05-14 7:39 ` Tetsuo Handa [this message]
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=21d52c65-4f18-46a2-be68-ff8487103e82@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).