From: Jens Axboe <axboe@kernel.dk>
To: Ammar Faizi <ammar.faizi@students.amikom.ac.id>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Bedirhan KURT <windowz414@gnuweeb.org>
Subject: Re: [PATCH v2 liburing] test: Add kworker-hang test
Date: Fri, 5 Nov 2021 17:41:55 -0600 [thread overview]
Message-ID: <687bd0c5-be36-6892-c1e5-4488548aab12@kernel.dk> (raw)
In-Reply-To: <CAGzmLMVvhkanBZYq-4PU0NeiPH8K8jhRBH+koqf-1gGrzXGjxg@mail.gmail.com>
On 11/5/21 5:35 PM, Ammar Faizi wrote:
> On Wed, Oct 20, 2021 at 7:52 PM Ammar Faizi
> <ammar.faizi@students.amikom.ac.id> wrote:
>>
>> Add kworker-hang test to reproduce this:
>>
>> [28335.037622] INFO: task kworker/u8:3:77596 blocked for more than 10 seconds.
>> [28335.037629] Tainted: G W OE 5.15.0-rc4-for-5.16-io-uring-00060-g4922ab639eb6 #4
>> [28335.037637] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> [28335.037642] task:kworker/u8:3 state:D stack: 0 pid:77596 ppid: 2 flags:0x00004000
>> [28335.037650] Workqueue: events_unbound io_ring_exit_work
>
> Hi Jens, will you take this patch? If yes, I will spin the v3 because
> this one no longer applies since the test/Makefile changed.
Yes I will, sorry it dropped off my radar. Please just respin it.
> This kworker hang bug still lives in Linux 5.15 stable anyway.
We just need to backport the fix, then it should be fixed there too :-)
--
Jens Axboe
next prev parent reply other threads:[~2021-11-05 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 19:07 [PATCH liburing] test: Add kworker-hang test Ammar Faizi
2021-10-20 12:51 ` [PATCH v2 " Ammar Faizi
2021-11-05 23:35 ` Ammar Faizi
2021-11-05 23:41 ` Jens Axboe [this message]
2021-11-06 0:58 ` [PATCH v3 " Ammar Faizi
2021-11-06 7:42 ` [PATCH v4 " Ammar Faizi
2021-11-06 11:37 ` [PATCH v5 " Ammar Faizi
2021-11-06 11:49 ` [PATCH v6 " Ammar Faizi
2021-11-09 5:44 ` Ammar Faizi
2021-11-09 14:47 ` Jens Axboe
2021-11-09 15:21 ` Ammar Faizi
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=687bd0c5-be36-6892-c1e5-4488548aab12@kernel.dk \
--to=axboe@kernel.dk \
--cc=ammar.faizi@students.amikom.ac.id \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=windowz414@gnuweeb.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;
as well as URLs for NNTP newsgroup(s).