From: Stefano Garzarella <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Kernel Hardening <[email protected]>,
Christian Brauner <[email protected]>,
[email protected], [email protected],
Alexander Viro <[email protected]>,
Stefan Hajnoczi <[email protected]>,
Jann Horn <[email protected]>, Jeff Moyer <[email protected]>,
Aleksa Sarai <[email protected]>, Sargun Dhillon <[email protected]>,
[email protected], Kees Cook <[email protected]>
Subject: [PATCH v6 0/3] io_uring: add restrictions to support untrusted applications and guests
Date: Thu, 27 Aug 2020 16:58:28 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
v6:
- moved restriction checks in a function [Jens]
- changed ret value handling in io_register_restrictions() [Jens]
v5: https://lore.kernel.org/io-uring/[email protected]/
v4: https://lore.kernel.org/io-uring/[email protected]/
v3: https://lore.kernel.org/io-uring/[email protected]/
RFC v2: https://lore.kernel.org/io-uring/[email protected]
RFC v1: https://lore.kernel.org/io-uring/[email protected]
Following the proposal that I send about restrictions [1], I wrote this series
to add restrictions in io_uring.
I also wrote helpers in liburing and a test case (test/register-restrictions.c)
available in this repository:
https://github.com/stefano-garzarella/liburing (branch: io_uring_restrictions)
Just to recap the proposal, the idea is to add some restrictions to the
operations (sqe opcode and flags, register opcode) to safely allow untrusted
applications or guests to use io_uring queues.
The first patch changes io_uring_register(2) opcodes into an enumeration to
keep track of the last opcode available.
The second patch adds IOURING_REGISTER_RESTRICTIONS opcode and the code to
handle restrictions.
The third patch adds IORING_SETUP_R_DISABLED flag to start the rings disabled,
allowing the user to register restrictions, buffers, files, before to start
processing SQEs.
Comments and suggestions are very welcome.
Thank you in advance,
Stefano
[1] https://lore.kernel.org/io-uring/20200609142406.upuwpfmgqjeji4lc@steredhat/
Stefano Garzarella (3):
io_uring: use an enumeration for io_uring_register(2) opcodes
io_uring: add IOURING_REGISTER_RESTRICTIONS opcode
io_uring: allow disabling rings during the creation
fs/io_uring.c | 172 ++++++++++++++++++++++++++++++++--
include/uapi/linux/io_uring.h | 60 +++++++++---
2 files changed, 215 insertions(+), 17 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-27 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 14:58 Stefano Garzarella [this message]
2020-08-27 14:58 ` [PATCH v6 1/3] io_uring: use an enumeration for io_uring_register(2) opcodes Stefano Garzarella
2020-08-27 14:58 ` [PATCH v6 2/3] io_uring: add IOURING_REGISTER_RESTRICTIONS opcode Stefano Garzarella
2021-01-03 14:26 ` Daurnimator
2021-01-07 8:39 ` Stefano Garzarella
2020-08-27 14:58 ` [PATCH v6 3/3] io_uring: allow disabling rings during the creation Stefano Garzarella
2020-09-08 13:44 ` Stefano Garzarella
2020-09-08 13:57 ` Jens Axboe
2020-09-08 14:10 ` Stefano Garzarella
2020-09-08 14:11 ` Jens Axboe
2020-08-28 3:01 ` [PATCH v6 0/3] io_uring: add restrictions to support untrusted applications and guests Jens Axboe
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] \
[email protected] \
[email protected] \
[email protected] \
[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