[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35f8d506-fb3b-94a5-8aab-f1bde0e5f48a@gmail.com>
Date: Sun, 2 May 2021 16:56:31 +0100
From: Pavel Begunkov <asml.silence@...il.com>
To: Palash Oswal <oswalpalash@...il.com>,
Hillf Danton <hdanton@...a.com>
Cc: Jens Axboe <axboe@...nel.dk>, io-uring@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
syzbot+11bf59db879676f59e52@...kaller.appspotmail.com
Subject: Re: INFO: task hung in io_uring_cancel_sqpoll
On 5/2/21 4:01 PM, Palash Oswal wrote:
> On Sun, May 2, 2021 at 4:04 PM Pavel Begunkov <asml.silence@...il.com> wrote:
>
>>> I tested against the HEAD b1ef997bec4d5cf251bfb5e47f7b04afa49bcdfe
>>
>> However, there is a bunch patches fixing sqpoll cancellations in
>> 5.13, all are waiting for backporting. and for-next doesn't trigger
>> the issue for me.
>>
>> Are you absolutely sure b1ef997bec4d5cf251bfb5e47f7b04afa49bcdfe
>> does hit it?
>>
>>> commit on for-next tree
>>> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/?h=for-next
>>> and the reproducer fails.
>
> Hi Pavel and Hillf,
>
> I believe there's a little misunderstanding, apologies. The reproducer
> does not trigger the bug on the for-next tree which has patches for
> 5.13. The reproducer process exits correctly. Likely one of those
> commits that will be back-ported to 5.12 will address this issue.
> When I wrote `the reproducer fails`, I meant to indicate that the bug
> is not triggered on for-next. I will word it better next time!
I see, great it's clarified
--
Pavel Begunkov
Powered by blists - more mailing lists