From: Greg KH <[email protected]>
To: Stefano Garzarella <[email protected]>
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCH 5.8] io_uring: ensure open/openat2 name is cleaned on cancelation
Date: Mon, 28 Sep 2020 19:33:25 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, Sep 28, 2020 at 05:35:07PM +0200, Stefano Garzarella wrote:
> From: Jens Axboe <[email protected]>
>
> [ Upstream commit f3cd4850504ff612d0ea77a0aaf29b66c98fcefe ]
>
> If we cancel these requests, we'll leak the memory associated with the
> filename. Add them to the table of ops that need cleaning, if
> REQ_F_NEED_CLEANUP is set.
>
> Cc: [email protected]
> Fixes: e62753e4e292 ("io_uring: call statx directly")
> Reviewed-by: Stefano Garzarella <[email protected]>
> Signed-off-by: Jens Axboe <[email protected]>
> Signed-off-by: Stefano Garzarella <[email protected]>
> ---
> fs/io_uring.c | 2 ++
> 1 file changed, 2 insertions(+)
Thanks, now queued up.
greg k-h
prev parent reply other threads:[~2020-09-28 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 15:35 [PATCH 5.8] io_uring: ensure open/openat2 name is cleaned on cancelation Stefano Garzarella
2020-09-28 17:33 ` Greg KH [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 \
[email protected] \
[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