From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH for-5.10] io_uring: remove req cancel in ->flush()
Date: Tue, 20 Oct 2020 17:29:30 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 20/10/2020 15:09, Jens Axboe wrote:
> On 10/19/20 5:40 PM, Pavel Begunkov wrote:
>> On 19/10/2020 21:08, Jens Axboe wrote:
>>> On 10/19/20 9:45 AM, Pavel Begunkov wrote:
>>>> Every close(io_uring) causes cancellation of all inflight requests
>>>> carrying ->files. That's not nice but was neccessary up until recently.
>>>> Now task->files removal is handled in the core code, so that part of
>>>> flush can be removed.
>>>
>>> Why not just keep the !data for task_drop? Would make the diff take
>>> away just the hunk we're interested in. Even adding a comment would be
>>> better, imho.
>>
>> That would look cleaner, but I just left what already was there. TBH,
>> I don't even entirely understand why exiting=!data. Looking up how
>> exit_files() works, it passes down non-NULL files to
>> put_files_struct() -> ... filp_close() -> f_op->flush().
>>
>> I'm curious how does this filp_close(file, files=NULL) happens?
>
> It doesn't, we just clear it internall to match all requests, not just
> files backed ones.
Then my "bool exiting = !data;" at the start doesn't make sense since
passed in @data is always non-NULL.
>
>> Moreover, if that's exit_files() which is interesting, then first
>> it calls io_uring_cancel_task_requests(), which should remove all
>> struct file from tctx->xa. I haven't tested it though.
>
> Yep, further cleanups are certainly possible there.
>
> I've queued this up, thanks.
>
--
Pavel Begunkov
next prev parent reply other threads:[~2020-10-20 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:45 [PATCH for-5.10] io_uring: remove req cancel in ->flush() Pavel Begunkov
2020-10-19 20:08 ` Jens Axboe
2020-10-19 23:40 ` Pavel Begunkov
2020-10-20 14:09 ` Jens Axboe
2020-10-20 16:29 ` Pavel Begunkov [this message]
2020-10-20 16:59 ` Jens Axboe
2020-10-22 6:42 ` Xiaoguang Wang
2020-10-22 11:44 ` Pavel Begunkov
2020-10-23 3:33 ` Xiaoguang Wang
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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