From: Daurnimator <[email protected]>
To: Stefano Garzarella <[email protected]>
Cc: Jens Axboe <[email protected]>,
Kernel Hardening <[email protected]>,
Christian Brauner <[email protected]>,
io-uring <[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: Re: [PATCH v6 2/3] io_uring: add IOURING_REGISTER_RESTRICTIONS opcode
Date: Mon, 4 Jan 2021 01:26:41 +1100 [thread overview]
Message-ID: <CAEnbY+fS8FXVeouOxN3uohTvo7fBi5r7TQCGBZUmG3MGJhBrYg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, 28 Aug 2020 at 00:59, Stefano Garzarella <[email protected]> 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?
next prev parent reply other threads:[~2021-01-03 14:27 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 [this message]
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 \
--in-reply-to=CAEnbY+fS8FXVeouOxN3uohTvo7fBi5r7TQCGBZUmG3MGJhBrYg@mail.gmail.com \
[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