From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
syzbot <syzbot+e333341d3d985e5173b2@syzkaller.appspotmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] [usb?] WARNING in io_get_cqe_overflow (2)
Date: Tue, 5 Nov 2024 01:20:15 +0000 [thread overview]
Message-ID: <768a51d0-8c63-4d9f-a636-c9cb52a0c4f4@gmail.com> (raw)
In-Reply-To: <74004a91-2753-45fc-88b4-8b2103f9a155@kernel.dk>
On 11/4/24 17:05, Jens Axboe wrote:
> On 11/4/24 10:03 AM, Jens Axboe wrote:
>> On 11/4/24 9:54 AM, Pavel Begunkov wrote:
>>> On 11/4/24 15:43, Jens Axboe wrote:
>>>> On 11/4/24 8:34 AM, Pavel Begunkov wrote:
>>>>> On 11/4/24 15:27, Pavel Begunkov wrote:
>>> ...
>>>>> Regardless, the rule with sth like that should be simpler,
>>>>> i.e. a ctx is getting killed => everything is run from fallback/kthread.
>>>>
>>>> I like it, and now there's another reason to do it. Can you out the
>>>> patch?
>>>
>>> Let's see if it works, hopefully will try today.
>>
>> I already tried it here fwiw, does fix the issue (as expected) and it
>> passes the full testing too.
>
> Forgot to include the basic reproducer I wrote for this report, it's
> below.
Thanks for testing.
I was just looking at the patch, and the fun part is that it depends on
failing tw off PF_KTHREAD tasks... Otherwise when the fallback executes
a request the original task could still be alive =>
(req->task->flags & PF_EXITING) check passes and the request continues
doing stuff from the kthread (with no mm and so).
A side note that it should be marginally better than before on the
cancellation front because we're killing task_work more eagerly
for a dying ctx but alive tasks.
I'll send the patch properly.
--
Pavel Begunkov
next prev parent reply other threads:[~2024-11-05 1:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 10:36 [syzbot] [io-uring?] [usb?] WARNING in io_get_cqe_overflow (2) syzbot
2024-11-04 11:31 ` syzbot
2024-11-04 13:13 ` Pavel Begunkov
2024-11-04 15:08 ` Jens Axboe
2024-11-04 15:27 ` Pavel Begunkov
2024-11-04 15:34 ` Pavel Begunkov
2024-11-04 15:43 ` Jens Axboe
2024-11-04 16:54 ` Pavel Begunkov
2024-11-04 17:03 ` Jens Axboe
2024-11-04 17:05 ` Jens Axboe
2024-11-05 1:20 ` Pavel Begunkov [this message]
2024-12-28 20:57 ` Jens Axboe
2024-12-28 20:57 ` syzbot
2024-12-28 20:58 ` Jens Axboe
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=768a51d0-8c63-4d9f-a636-c9cb52a0c4f4@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+e333341d3d985e5173b2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@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