[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Jan 2021 01:26:41 +1100
From: Daurnimator <quae@...rnimator.com>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>, Kernel Hardening <kernel-hardening@...ts.openwall.com>,
Christian Brauner <christian.brauner@...ntu.com>, io-uring <io-uring@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>, Stefan Hajnoczi <stefanha@...hat.com>,
Jann Horn <jannh@...gle.com>, Jeff Moyer <jmoyer@...hat.com>, Aleksa Sarai <asarai@...e.de>,
Sargun Dhillon <sargun@...gun.me>, linux-kernel@...r.kernel.org,
Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH v6 2/3] io_uring: add IOURING_REGISTER_RESTRICTIONS opcode
On Fri, 28 Aug 2020 at 00:59, Stefano Garzarella <sgarzare@...hat.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?
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
