diff options
| author | Hari Bathini <hbathini@linux.ibm.com> | 2026-03-03 23:40:27 +0530 |
|---|---|---|
| committer | Madhavan Srinivasan <maddy@linux.ibm.com> | 2026-03-07 16:02:26 +0530 |
| commit | 3727d6ec13665c1d99bf6dedb107104368ba42b4 (patch) | |
| tree | fb2ee1a40545c17c7a326e5fb4178283daa26786 /tools/perf/scripts/python | |
| parent | 157820264ac3dadfafffad63184b883eb28f9ae0 (diff) | |
| download | linux-3727d6ec13665c1d99bf6dedb107104368ba42b4.tar.gz linux-3727d6ec13665c1d99bf6dedb107104368ba42b4.zip | |
powerpc64/bpf: use consistent tailcall offset in trampoline
Ideally, the offset used to load the tail call info field and to find
the pass by reference address for tail call field should be the same.
But while setting up the tail call info in the trampoline, this was
not followed. This can be misleading and can lead to unpredictable
results if and when bpf_has_stack_frame() ends up returning true
for trampoline frame. Since commit 15513beeb673 ("powerpc64/bpf:
Moving tail_call_cnt to bottom of frame") and commit 2ed2d8f6fb38
("powerpc64/bpf: Support tailcalls with subprogs") ensured tail call
field is at the bottom of the stack frame for BPF programs as well as
BPF trampoline, avoid relying on bpf_jit_stack_tailcallinfo_offset()
and bpf_has_stack_frame() for trampoline frame and always calculate
tail call field offset with reference to older frame.
Fixes: 2ed2d8f6fb38 ("powerpc64/bpf: Support tailcalls with subprogs")
Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
Link: https://patch.msgid.link/20260303181031.390073-4-hbathini@linux.ibm.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
