From: Jens Axboe <axboe@kernel.dk>
To: Sanan Hasanov <sanan.hasanov@Knights.ucf.edu>,
"asml.silence@gmail.com" <asml.silence@gmail.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "syzkaller@googlegroups.com" <syzkaller@googlegroups.com>,
"contact@pgazz.com" <contact@pgazz.com>
Subject: Re: INFO: task hung in io_ring_exit_work
Date: Wed, 1 Mar 2023 07:53:57 -0700 [thread overview]
Message-ID: <5ff2b3c0-eb96-c423-dcee-1bdf6604e9df@kernel.dk> (raw)
In-Reply-To: <IA1PR07MB9830E72E8A3426B8151185BAABAF9@IA1PR07MB9830.namprd07.prod.outlook.com>
On 2/26/23 11:23 PM, Sanan Hasanov wrote:
> Good day, dear maintainers,
>
> We found a bug using a modified kernel configuration file used by syzbot.
>
> We enhanced the coverage of the configuration file using our tool, klocalizer.
>
> Kernel Branch: 6.2.0-next-20230225
> Kernel config: https://drive.google.com/file/d/1NS9N8rvftQ7BouImn2OVnC96qrNhAeuO/view?usp=share_link
> C Reproducer: Unfortunately, there is no reproducer for this bug yet.
Not sure what we're supposed to do with this, without a syzbot or
c reproducer? You can get into this condition if you SIGSTOP the
task so it can't complete its task_work, for example. But impossible
to glean anything from this report.
--
Jens Axboe
next prev parent reply other threads:[~2023-03-01 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 6:23 INFO: task hung in io_ring_exit_work Sanan Hasanov
2023-03-01 14:53 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-14 2:27 Hao Sun
2021-10-14 10:00 ` Pavel Begunkov
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=5ff2b3c0-eb96-c423-dcee-1bdf6604e9df@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=contact@pgazz.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanan.hasanov@Knights.ucf.edu \
--cc=syzkaller@googlegroups.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