From: adubey <adubey@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
bpf@vger.kernel.org, Madhavan Srinivasan <maddy@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Saket Kumar Bhaskar <skb99@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 2/5] powerpc64/bpf: fix the address returned by bpf_get_func_ip
Date: Sun, 22 Feb 2026 17:51:56 +0530 [thread overview]
Message-ID: <1c1e950c3513176c99a2a9b027c3be21@linux.ibm.com> (raw)
In-Reply-To: <20260220063933.196141-3-hbathini@linux.ibm.com>
On 2026-02-20 12:09, Hari Bathini wrote:
> bpf_get_func_ip() helper function returns the address of the traced
> function. It relies on the IP address stored at ctx - 16 by the bpf
> trampoline. On 64-bit powerpc, this address is recovered from LR
> accounting for OOL trampoline. But the address stored here was off
> by 4-bytes. Ensure the address is the actual start of the traced
> function.
>
> Reported-by: Abhishek Dubey <adubey@linux.ibm.com>
> Fixes: d243b62b7bd3 ("powerpc64/bpf: Add support for bpf trampolines")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> ---
>
> * No changes since v1.
>
>
> arch/powerpc/net/bpf_jit_comp.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/arch/powerpc/net/bpf_jit_comp.c
> b/arch/powerpc/net/bpf_jit_comp.c
> index 987cd9fb0f37..fb6cc1f832a8 100644
> --- a/arch/powerpc/net/bpf_jit_comp.c
> +++ b/arch/powerpc/net/bpf_jit_comp.c
> @@ -786,8 +786,8 @@ static int __arch_prepare_bpf_trampoline(struct
> bpf_tramp_image *im, void *rw_im
> * [ reg argN ]
> * [ ... ]
> * regs_off [ reg_arg1 ] prog ctx
> context
prog ctx context/prog_ctx context/prog_ctx, to be in sync with tags
below.
please refer s390's field tagging
> - * nregs_off [ args count ]
> - * ip_off [ traced function ]
> + * nregs_off [ args count ] ((u64
> *)prog_ctx)[-1]
> + * ip_off [ traced function ] ((u64
> *)prog_ctx)[-2]
> * [ ... ]
> * run_ctx_off [ bpf_tramp_run_ctx ]
> * [ reg argN ]
> @@ -895,7 +895,7 @@ static int __arch_prepare_bpf_trampoline(struct
> bpf_tramp_image *im, void *rw_im
>
> bpf_trampoline_save_args(image, ctx, func_frame_offset, nr_regs,
> regs_off);
>
> - /* Save our return address */
> + /* Save our LR/return address */
> EMIT(PPC_RAW_MFLR(_R3));
> if (IS_ENABLED(CONFIG_PPC_FTRACE_OUT_OF_LINE))
> EMIT(PPC_RAW_STL(_R3, _R1, alt_lr_off));
> @@ -903,24 +903,29 @@ static int __arch_prepare_bpf_trampoline(struct
> bpf_tramp_image *im, void *rw_im
> EMIT(PPC_RAW_STL(_R3, _R1, bpf_frame_size + PPC_LR_STKOFF));
>
> /*
> - * Save ip address of the traced function.
> - * We could recover this from LR, but we will need to address for
> OOL trampoline,
> - * and optional GEP area.
> + * Get IP address of the traced function.
Get/Derive
> + * In case of CONFIG_PPC_FTRACE_OUT_OF_LINE or BPF program, LR
> + * points to the instruction after the 'bl' instruction in the OOL
> stub.
> + * Refer to ftrace_init_ool_stub() and bpf_arch_text_poke() for OOL
> stub
> + * of kernel functions and bpf programs respectively.
> + * Recover kernel function/bpf program address from the unconditional
> + * branch instruction at the end of OOL stub.
> */
> if (IS_ENABLED(CONFIG_PPC_FTRACE_OUT_OF_LINE) || flags &
> BPF_TRAMP_F_IP_ARG) {
> EMIT(PPC_RAW_LWZ(_R4, _R3, 4));
Please add comment what R4 points to; for easy referencing
> EMIT(PPC_RAW_SLWI(_R4, _R4, 6));
> EMIT(PPC_RAW_SRAWI(_R4, _R4, 6));
> EMIT(PPC_RAW_ADD(_R3, _R3, _R4));
> - EMIT(PPC_RAW_ADDI(_R3, _R3, 4));
> }
>
> if (flags & BPF_TRAMP_F_IP_ARG)
> EMIT(PPC_RAW_STL(_R3, _R1, ip_off));
>
> - if (IS_ENABLED(CONFIG_PPC_FTRACE_OUT_OF_LINE))
> + if (IS_ENABLED(CONFIG_PPC_FTRACE_OUT_OF_LINE)) {
> /* Fake our LR for unwind */
> + EMIT(PPC_RAW_ADDI(_R3, _R3, 4));
> EMIT(PPC_RAW_STL(_R3, _R1, bpf_frame_size + PPC_LR_STKOFF));
> + }
>
> /* Save function arg count -- see bpf_get_func_arg_cnt() */
> EMIT(PPC_RAW_LI(_R3, nr_regs));
-Abhishek
next prev parent reply other threads:[~2026-02-22 12:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 6:39 [PATCH v2 0/5] powerpc64/bpf: various fixes Hari Bathini
2026-02-20 6:39 ` [PATCH v2 1/5] powerpc64/bpf: do not increment tailcall count when prog is NULL Hari Bathini
2026-02-21 3:40 ` Venkat Rao Bagalkote
2026-02-20 6:39 ` [PATCH v2 2/5] powerpc64/bpf: fix the address returned by bpf_get_func_ip Hari Bathini
2026-02-21 3:41 ` Venkat Rao Bagalkote
2026-02-22 12:21 ` adubey [this message]
2026-02-20 6:39 ` [PATCH v2 3/5] powerpc64/bpf: use consistent tailcall offset in trampoline Hari Bathini
2026-02-22 13:07 ` adubey
2026-03-03 13:43 ` Hari Bathini
2026-02-20 6:39 ` [PATCH v2 4/5] powerpc64/bpf: remove BPF redzone protection in trampoline stack Hari Bathini
2026-02-21 3:43 ` Venkat Rao Bagalkote
2026-02-20 6:39 ` [PATCH v2 5/5] powerpc64/bpf: fix handling of BPF stack in exception callback Hari Bathini
2026-02-23 9:03 ` adubey
2026-03-03 13:46 ` Hari Bathini
2026-02-24 12:28 ` adubey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c1e950c3513176c99a2a9b027c3be21@linux.ibm.com \
--to=adubey@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=skb99@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=venkat88@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.