From: Lee Jones <lee.jones@linaro.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Patch for 5.10-stable
Date: Thu, 19 May 2022 15:41:58 +0100 [thread overview]
Message-ID: <YoZXNjl8LmcWCQa9@google.com> (raw)
In-Reply-To: <543c3909-a7b6-23ac-2c2e-ce10dd2433e8@kernel.dk>
On Thu, 19 May 2022, Jens Axboe wrote:
> Hi,
>
> Can we get this queued up for 5.10-stable? Thanks!
>
> From b1da21187de121e2ed2dc2e0c70d5aabce469691 Mon Sep 17 00:00:00 2001
> From: Jens Axboe <axboe@kernel.dk>
> Date: Thu, 19 May 2022 06:05:27 -0600
> Subject: [PATCH] io_uring: always grab file table for deferred statx
>
> Lee reports that there's a use-after-free of the process file table.
> There's an assumption that we don't need the file table for some
> variants of statx invocation, but that turns out to be false and we
> end up with not grabbing a reference for the request even if the
> deferred execution uses it.
>
> Get rid of the REQ_F_NO_FILE_TABLE optimization for statx, and always
> grab that reference.
>
> This issues doesn't exist upstream since the native workers got
> introduced with 5.12.
>
> Link: https://lore.kernel.org/io-uring/YoOJ%2FT4QRKC+fAZE@google.com/
> Reported-by: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Tested-by: Lee Jones <lee.jones@linaro.org>
> ---
> fs/io_uring.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 4330603eae35..3ecf71151fb1 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -4252,12 +4252,8 @@ static int io_statx(struct io_kiocb *req, bool force_nonblock)
> struct io_statx *ctx = &req->statx;
> int ret;
>
> - if (force_nonblock) {
> - /* only need file table for an actual valid fd */
> - if (ctx->dfd == -1 || ctx->dfd == AT_FDCWD)
> - req->flags |= REQ_F_NO_FILE_TABLE;
> + if (force_nonblock)
> return -EAGAIN;
> - }
>
> ret = do_statx(ctx->dfd, ctx->filename, ctx->flags, ctx->mask,
> ctx->buffer);
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2022-05-19 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:09 Patch for 5.10-stable Jens Axboe
2022-05-19 12:36 ` Greg Kroah-Hartman
2022-05-19 12:37 ` Jens Axboe
2022-05-19 14:41 ` Lee Jones [this message]
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=YoZXNjl8LmcWCQa9@google.com \
--to=lee.jones@linaro.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.