[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5ff2b3c0-eb96-c423-dcee-1bdf6604e9df@kernel.dk>
Date: Wed, 1 Mar 2023 07:53:57 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Sanan Hasanov <sanan.hasanov@...ghts.ucf.edu>,
"asml.silence@...il.com" <asml.silence@...il.com>,
"io-uring@...r.kernel.org" <io-uring@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "syzkaller@...glegroups.com" <syzkaller@...glegroups.com>,
"contact@...zz.com" <contact@...zz.com>
Subject: Re: INFO: task hung in io_ring_exit_work
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
Powered by blists - more mailing lists