On 8/27/20 8:58 AM, Stefano Garzarella wrote: > v6: > - moved restriction checks in a function [Jens] > - changed ret value handling in io_register_restrictions() [Jens] > > v5: > https://lore.kernel.org/io-uring/20200827134044.82821-1-sgarz...@redhat.com/ > v4: > https://lore.kernel.org/io-uring/20200813153254.93731-1-sgarz...@redhat.com/ > v3: > https://lore.kernel.org/io-uring/20200728160101.48554-1-sgarz...@redhat.com/ > RFC v2: > https://lore.kernel.org/io-uring/20200716124833.93667-1-sgarz...@redhat.com > RFC v1: > https://lore.kernel.org/io-uring/20200710141945.129329-1-sgarz...@redhat.com > > 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.
Applied, thanks. -- Jens Axboe
