From: Hillf Danton <hdanton@sina.com>
To: Sam Sun <samsun1006219@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
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: Wed, 15 May 2024 06:41:17 +0800 [thread overview]
Message-ID: <20240514224117.3191-1-hdanton@sina.com> (raw)
In-Reply-To: <CAEkJfYPH3SJ6J3kLSjMGqkWOzgbgKZV_f2Hq05cpZZv7RmhvOg@mail.gmail.com>
On Tue, 14 May 2024 20:07:34 +0800 Sam Sun <samsun1006219@gmail.com>
>
> I tried to run
>
> # echo 0 > /proc/sys/kernel/hung_task_all_cpu_backtrace
>
> before running the reproducer, the kernel stops panic. But still, even
> if I terminate the execution of the reproducer, kernel continues
> dumping task hung logs. After setting bung_task_all_cpu_backtrace back
> to 1, it panic immediately during next dump. So I guess it is still a
> task hung instead of general protection fault.
Given kworker/u10:2:53 blocked for more than 143 seconds, or the subject
line, how could it trigger gpf?
next prev parent reply other threads:[~2024-05-14 22:41 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
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 [this message]
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=20240514224117.3191-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