From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: krisman@suse.de
Subject: [PATCHSET RFC v2 0/3] Per-task io_uring opcode restrictions
Date: Fri, 9 Jan 2026 11:48:24 -0700 [thread overview]
Message-ID: <20260109185155.88150-1-axboe@kernel.dk> (raw)
Hi,
For details on this patchset, see the v1 posting here:
https://lore.kernel.org/io-uring/20260108202944.288490-1-axboe@kernel.dk/
This code can also be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git/log/?h=io_uring-task-restrictions
and a corresponding liburing branch here:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/liburing.git/log/?h=task-restrictions
with basic support and test cases.
include/linux/io_uring.h | 2 +-
include/linux/io_uring_types.h | 2 +
include/linux/sched.h | 1 +
include/uapi/linux/io_uring.h | 18 ++++++
io_uring/io_uring.c | 10 +++
io_uring/register.c | 110 ++++++++++++++++++++++++++++++---
io_uring/tctx.c | 25 +++++---
kernel/fork.c | 4 ++
8 files changed, 153 insertions(+), 19 deletions(-)
Changes since v1
- Remove IORING_REG_RESTRICTIONS_INHERIT flag, restrictions are
inherited across fork by default now.
- Allow original creator of a restriction set to unregister it as well.
- Add IORING_REG_RESTRICTIONS_MASK flag, which allows anyone to further
restrict the currently assigned restriction set.
- Ensure failure operations restore old set.
- Add more test cases on the liburing side.
--
Jens Axboe
next reply other threads:[~2026-01-09 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 18:48 Jens Axboe [this message]
2026-01-09 18:48 ` [PATCH 1/3] io_uring: allow registration of per-task restrictions Jens Axboe
2026-01-09 18:48 ` [PATCH 2/3] io_uring/register: add MASK support for task filter set Jens Axboe
2026-01-09 18:48 ` [PATCH 3/3] io_uring/register: allow original task restrictions owner to unregister Jens Axboe
2026-01-13 0:10 ` Gabriel Krisman Bertazi
2026-01-13 18:25 ` 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=20260109185155.88150-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.