Re: [PATCH bpf-next v1 01/14] bpf: Split arena kfunc and struct_ops JIT capabilities
| Newsgroups | org.kernel.vger.bpf |
|---|---|
| Message-ID | <8cbc0a547ead611386fa44b6cf6b027dc371a3ffab68d8b0d6b6929d87288c55@mail.kernel.org> |
> bpf: Split arena kfunc and struct_ops JIT capabilities > > Arena pointer kfunc calls and struct_ops callbacks need different JIT > support. The former rebases BPF arena offsets before a kfunc call, while > the latter converts kernel pointers when an indirect trampoline builds a > callback context. > > A single bpf_jit_supports_arena_args() hook forces an architecture to > implement both paths at once. That ties bpf_arena_alloc_pages() > conversion to struct_ops trampoline support and prevents the paths from > being enabled and reviewed independently. > > Replace it with separate kfunc and struct_ops capability hooks. Make the > verifier query the hook for the path it is checking, and have x86-64 and > arm64 advertise both capabilities to preserve their current behavior. > > Signed-off-by: Kumar Kartikeya Dwivedi <[email protected]> This isn't a bug, but since bpf_arena_alloc_pages() still takes addr__ign at this point in the series and only picks up the __arena__nullable suffix in a later patch, would it read more clearly to phrase this as what the split enables for the following patches, or to point at an argument that is already suffixed today? --- AI reviewed your patch. Please fix the bug or email reply why it's not a bug. See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32538351576