From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: [PATCH 0/2] address resourse leaks
Date: Sat, 8 Feb 2020 13:28:01 +0300 [thread overview]
Message-ID: <[email protected]> (raw)
This fixes the last prep/submission-related leaking hole I found.
The first patch is only for read/write/send/recv, so may be 5.5-ported
if needed. The second one doing the same but for openat{,2} and statx.
Pavel Begunkov (2):
io_uring: fix double prep iovec leak
io_uring: fix openat/statx's filename leak
fs/io_uring.c | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 deletions(-)
--
2.24.0
next reply other threads:[~2020-02-08 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 10:28 Pavel Begunkov [this message]
2020-02-08 10:28 ` [PATCH 1/2] io_uring: fix double prep iovec leak Pavel Begunkov
2020-02-08 10:28 ` [PATCH 2/2] io_uring: fix openat/statx's filename leak 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