Skip to content

io_uring op probing fixes

Gabriel Krisman Bertazi io-uring 1 version Applied

Status from this message: Applied, thanks!

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 5 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3io_uring: Fix probe of disabled operationsio_uring/opdef.c io_uring/opdef.h io_uring/register.c+11 -30 replies
2/3io_uring: Allocate only necessary memory in io_probeio_uring/register.c+3 -40 replies
3/3io_uring: Don't read userspace data in io_probeio_uring/register.c+1 -103 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] io_uring op probing fixes

Hi Jens,

I didn't know this interface existed until today, when I started looking at creating exactly this feature. My goal is to know which operation supports which modes (registered buffers, bundled writes, iopoll). Now that I know it exists, I might just expose the extra information through io_uring_probe_op->flags, instead of adding a new operation. What do you think?

Anyway, this patchset is not implementing that. Patch 1 fixes an issue with the existing interface. Patches 2 and 3 are small cleanups to the same path, since I was already looking at it.

I tested it with a !CONFIG_NET kernel to have some disabled operations. It also survived the liburing testsuite.

Gabriel Krisman Bertazi (3):
io_uring: Fix probe of disabled operations
io_uring: Allocate only necessary memory in io_probe
io_uring: Don't read userspace data in io_probe

 io_uring/opdef.c    |  8 ++++++++
 io_uring/opdef.h    |  4 ++--
 io_uring/register.c | 20 +++++---------------
 3 files changed, 15 insertions(+), 17 deletions(-)
Signature · 1 line
2.45.2