[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7faa04f8-cd98-7d8a-2e54-e84e1fe742f7@gmail.com>
Date: Mon, 13 Sep 2021 09:30:09 +0100
From: Pavel Begunkov <asml.silence@...il.com>
To: Hao Sun <sunhao.th@...il.com>, Jens Axboe <axboe@...nel.dk>
Cc: io-uring@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: INFO: task hung in io_uring_cancel_generic
On 9/13/21 3:26 AM, Hao Sun wrote:
> Hi
>
> Healer found a C reproducer for this crash ("INFO: task hung in
> io_ring_exit_work").
>
> HEAD commit: 4b93c544e90e-thunderbolt: test: split up test cases
> git tree: upstream
> console output:
> https://drive.google.com/file/d/1NswMU2yMRTc8-EqbZcVvcJejV92cuZIk/view?usp=sharing
> kernel config: https://drive.google.com/file/d/1c0u2EeRDhRO-ZCxr9MP2VvAtJd6kfg-p/view?usp=sharing
> C reproducer: https://drive.google.com/file/d/170wk5_T8mYDaAtDcrdVi2UU9_dW1894s/view?usp=sharing
> Syzlang reproducer:
> https://drive.google.com/file/d/1eo-jAS9lncm4i-1kaCBkexrjpQHXboBq/view?usp=sharing
>
> If you fix this issue, please add the following tag to the commit:
> Reported-by: Hao Sun <sunhao.th@...il.com>
I don't see the repro using io_uring at all. Can it be because of
the delay before the warning shows itself? 120 secs, this appeared
after 143.
[...]
--
Pavel Begunkov
Powered by blists - more mailing lists