From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH 0/3] changes around fixed rsrc
Date: Fri, 20 Aug 2021 10:36:34 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
1-2 put some limits on the fixed file tables sizes, files and
buffers.
3/3 adds compatibility checks for ->splice_fd_in, for all requests
buy rw and some others, see the patch message.
All based on 5.15 and merked stable, looks to me as the best way.
Pavel Begunkov (3):
io_uring: limit fixed table size by RLIMIT_NOFILE
io_uring: place fixed tables under memcg limits
io_uring: add ->splice_fd_in checks
fs/io_uring.c | 61 ++++++++++++++++++++++++++++++---------------------
1 file changed, 36 insertions(+), 25 deletions(-)
--
2.32.0
next reply other threads:[~2021-08-20 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 9:36 Pavel Begunkov [this message]
2021-08-20 9:36 ` [PATCH 1/3] io_uring: limit fixed table size by RLIMIT_NOFILE Pavel Begunkov
2021-08-20 9:36 ` [PATCH 2/3] io_uring: place fixed tables under memcg limits Pavel Begunkov
2021-08-20 9:36 ` [PATCH 3/3] io_uring: add ->splice_fd_in checks Pavel Begunkov
2021-08-21 13:18 ` [PATCH 0/3] changes around fixed rsrc Jens Axboe
2021-08-21 14:25 ` 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] \
/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