From: Stefano Garzarella <sgarzare@redhat.com>
To: Daurnimator <quae@daurnimator.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
io-uring <io-uring@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jann Horn <jannh@google.com>, Jeff Moyer <jmoyer@redhat.com>,
Aleksa Sarai <asarai@suse.de>, Sargun Dhillon <sargun@sargun.me>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v6 2/3] io_uring: add IOURING_REGISTER_RESTRICTIONS opcode
Date: Thu, 7 Jan 2021 09:39:32 +0100 [thread overview]
Message-ID: <20210107083932.ho6vo5g5hmdohwqt@steredhat> (raw)
In-Reply-To: <CAEnbY+fS8FXVeouOxN3uohTvo7fBi5r7TQCGBZUmG3MGJhBrYg@mail.gmail.com>
On Mon, Jan 04, 2021 at 01:26:41AM +1100, Daurnimator wrote:
>On Fri, 28 Aug 2020 at 00:59, Stefano Garzarella <sgarzare@redhat.com> wrote:
>> + __u8 register_op; /* IORING_RESTRICTION_REGISTER_OP */
>
>Can you confirm that this intentionally limited the future range of
>IORING_REGISTER opcodes to 0-255?
>
It was based on io_uring_probe, so we used u8 for opcodes, but we have
room to extend it in the future.
So, for now, this allow to register restrictions up to 255
IORING_REGISTER opcode.
next prev parent reply other threads:[~2021-01-07 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 14:58 [PATCH v6 0/3] io_uring: add restrictions to support untrusted applications and guests Stefano Garzarella
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 [this message]
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 \
--in-reply-to=20210107083932.ho6vo5g5hmdohwqt@steredhat \
--to=sgarzare@redhat.com \
--cc=asarai@suse.de \
--cc=axboe@kernel.dk \
--cc=christian.brauner@ubuntu.com \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=jmoyer@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quae@daurnimator.com \
--cc=sargun@sargun.me \
--cc=stefanha@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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