io_uring: track restrictions separately for IORING_OP and IORING_REGISTER

Browse source

It's quite likely that only register opcode restrictions exists, in
which case we'd never need to check the normal opcodes. Split
ctx->restricted into two separate fields, one for I/O opcodes, and one
for register opcodes.

Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

...

This commit is contained in:

Jens Axboe 2026-01-12 08:14:45 -07:00

parent 991fb85a1d

commit d6406c45f1

3 changed files with 22 additions and 9 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

8

include/linux/io_uring_types.h

View file

4

io_uring/io_uring.c

View file

19

io_uring/register.c

View file