diff options
| author | Pavel Begunkov <asml.silence@gmail.com> | 2026-06-02 11:08:25 +0100 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2026-06-02 11:20:21 -0600 |
| commit | ec02fe217fa66d79f8a65e8d28be9295c7f85093 (patch) | |
| tree | 2b1b98d57278925e8d811850f106f6e6101b187b /io_uring/loop.c | |
| parent | 29bef9934b2521f787bb15dd1985d4c0d12ae02a (diff) | |
io_uring/bpf-ops: restrict ctx access to BPF
BPF programs should have no need in looking into struct io_ring_ctx, if
anything, most of such cases would be anti patterns like looking up ring
indices directly via the context.
Replace it with a new empty structure, which is just an alias to struct
io_ring_ctx. It'll create a new BTF type and fail verification if a BPF
program tries to access it (beyond the first byte). It'll also give more
flexibility for the future, and otherwise it can be made aligned with
io_ring_ctx as before with struct groups if ever needed or extended in a
different way.
Fixes: d0e437b76bd3c ("io_uring/bpf-ops: implement loop_step with BPF struct_ops")
Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Link: https://patch.msgid.link/5f6ca3649e9e0bae8667db4357e28dd00cd07901.1780394491.git.asml.silence@gmail.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'io_uring/loop.c')
| -rw-r--r-- | io_uring/loop.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/io_uring/loop.c b/io_uring/loop.c index 31843cc3e451..bbbb6ef14e6a 100644 --- a/io_uring/loop.c +++ b/io_uring/loop.c @@ -49,7 +49,7 @@ static int __io_run_loop(struct io_ring_ctx *ctx) if (unlikely(!ctx->loop_step)) return -EFAULT; - step_res = ctx->loop_step(ctx, &lp); + step_res = ctx->loop_step(io_loop_mangle_ctx(ctx), &lp); if (step_res == IOU_LOOP_STOP) break; if (step_res != IOU_LOOP_CONTINUE) |