Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 13 Aug 2020 17:32:51 +0200
From: Stefano Garzarella <>
To: Jens Axboe <>
Cc: Christian Brauner <>,
	Jann Horn <>,
	Jeff Moyer <>,,
	Sargun Dhillon <>,
	Kees Cook <>,
	Alexander Viro <>,
	Kernel Hardening <>,
	Stefan Hajnoczi <>,,
	Aleksa Sarai <>,
Subject: [PATCH v4 0/3] io_uring: add restrictions to support untrusted
 applications and guests

 - rebased on top of io_uring-5.9
 - fixed io_uring_enter() exit path when ring is disabled

RFC v2:
RFC v1:

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.=
available in this repository: (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 Garzarella (3):
  io_uring: use an enumeration for io_uring_register(2) opcodes
  io_uring: allow disabling rings during the creation

 fs/io_uring.c                 | 160 ++++++++++++++++++++++++++++++++--
 include/uapi/linux/io_uring.h |  60 ++++++++++---
 2 files changed, 203 insertions(+), 17 deletions(-)


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.