From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
io-uring <[email protected]>, Jann Horn <[email protected]>
Subject: Re: [RFC] .flush and io_uring_cancel_files
Date: Tue, 26 May 2020 15:12:39 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/26/20 12:09 PM, Pavel Begunkov wrote:
> It looks like taking ->uring_lock should work like kind of grace
> period for struct files_struct and io_uring_flush(), and that would
> solve the race with "fcheck(ctx->ring_fd) == ctx->ring_file".
>
> Can you take a look? If you like it, I'll send a proper patch
> and a bunch of cleanups on top.
Adding Jann.
>
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index a3dbd5f40391..012af200dc72 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -5557,12 +5557,11 @@ static int io_grab_files(struct io_kiocb *req)
> * the fd has changed since we started down this path, and disallow
> * this operation if it has.
> */
> - if (fcheck(ctx->ring_fd) == ctx->ring_file) {
> - list_add(&req->inflight_entry, &ctx->inflight_list);
> - req->flags |= REQ_F_INFLIGHT;
> - req->work.files = current->files;
> - ret = 0;
> - }
> + list_add(&req->inflight_entry, &ctx->inflight_list);
> + req->flags |= REQ_F_INFLIGHT;
> + req->work.files = current->files;
> + ret = 0;
> +
> spin_unlock_irq(&ctx->inflight_lock);
> rcu_read_unlock();
>
> @@ -7479,6 +7478,10 @@ static int io_uring_release(struct inode *inode, struct
> file *file)
> static void io_uring_cancel_files(struct io_ring_ctx *ctx,
> struct files_struct *files)
> {
> + /* wait all submitters that can race for @files */
> + mutex_lock(&ctx->uring_lock);
> + mutex_unlock(&ctx->uring_lock);
> +
> while (!list_empty_careful(&ctx->inflight_list)) {
> struct io_kiocb *cancel_req = NULL, *req;
> DEFINE_WAIT(wait);
>
--
Jens Axboe
next prev parent reply other threads:[~2020-05-26 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 18:09 [RFC] .flush and io_uring_cancel_files Pavel Begunkov
2020-05-26 21:12 ` Jens Axboe [this message]
2020-05-26 22:04 ` Jann Horn
2020-05-27 10:13 ` Pavel Begunkov
2020-05-27 18:04 ` Jann Horn
2020-05-29 8:09 ` Pavel Begunkov
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] \
[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