diff options
author | Alexei Starovoitov <ast@kernel.org> | 2025-05-14 17:48:57 -0700 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2025-05-14 17:50:37 -0700 |
commit | 9325d53fe9adff354b6a93fda5f38c165947da0f (patch) | |
tree | e521f17306c7cb77eba2977fee7dce7f654e2deb /scripts/lib/kdoc/kdoc_re.py | |
parent | 5f55f2168432298f5a55294831ab6a76a10cb3c3 (diff) | |
parent | 8e57cf09c84cac99eb31354a3cc70f8b8981bfc2 (diff) |
Merge branch 's390-bpf-remove-the-orig_call-null-check'
Ilya Leoshkevich says:
====================
I've been looking at fixing the tailcall_bpf2bpf_hierarchy failures on
s390. One of the challenges is that when a BPF trampoline calls a BPF
prog A, the prologue of A sets the tail call count to 0. Therefore it
would be useful to know whether the trampoline is attached to some
other BPF prog B, in which case A should be called using an offset
equal to tail_call_start, bypassing the tail call count initialization.
The trampoline attachment point is passed to trampoline functions via
the orig_call variable. Unfortunately in the case of calculating the
size of a struct_ops trampoline it's NULL, and I could not think of a
good reason to have it this way. This series makes it always non-NULL.
====================
Link: https://patch.msgid.link/20250512221911.61314-1-iii@linux.ibm.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_re.py')
0 files changed, 0 insertions, 0 deletions