From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 5.18] io_uring: fix leaking uid in files registration
Date: Fri, 25 Mar 2022 16:07:40 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <accee442376f33ce8aaebb099d04967533efde92.1648226048.git.asml.silence@gmail.com>
On Fri, 25 Mar 2022 16:36:31 +0000, Pavel Begunkov wrote:
> When there are no files for __io_sqe_files_scm() to process in the
> range, it'll free everything and return. However, it forgets to put uid.
>
>
Applied, thanks!
[1/1] io_uring: fix leaking uid in files registration
commit: c86d18f4aa93e0e66cda0e55827cd03eea6bc5f8
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-03-25 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:36 [PATCH 5.18] io_uring: fix leaking uid in files registration Pavel Begunkov
2022-03-25 22:07 ` Jens Axboe [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=164824606076.470461.2361305622685411284.b4-ty@kernel.dk \
[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