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

 - moved restriction checks in a function [Jens]
 - changed ret value handling in io_register_restrictions() [Jens]

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.c)
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                 | 172 ++++++++++++++++++++++++++++++++--
 include/uapi/linux/io_uring.h |  60 +++++++++---
 2 files changed, 215 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.