From: Stanislav Fomichev <sdf@google.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
bpf@vger.kernel.org, "Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"KP Singh" <kpsingh@chromium.org>, "Hao Luo" <haoluo@google.com>,
"Xu Kuohai" <xukuohai@huawei.com>,
"Will Deacon" <will@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Pu Lehui" <pulehui@huawei.com>, "Björn Töpel" <bjorn@kernel.org>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Lee Jones" <lee@kernel.org>
Subject: Re: [PATCHv2 bpf 1/2] bpf: Add checkip argument to bpf_arch_text_poke
Date: Tue, 28 Nov 2023 13:24:14 -0800 [thread overview]
Message-ID: <ZWZafkt97qhgHynh@google.com> (raw)
In-Reply-To: <20231128092850.1545199-2-jolsa@kernel.org>
On 11/28, Jiri Olsa wrote:
> We need to be able to skip ip address check for caller in following
> changes. Adding checkip argument to allow that.
>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> arch/arm64/net/bpf_jit_comp.c | 3 ++-
> arch/riscv/net/bpf_jit_comp64.c | 5 +++--
> arch/s390/net/bpf_jit_comp.c | 3 ++-
> arch/x86/net/bpf_jit_comp.c | 24 +++++++++++++-----------
> include/linux/bpf.h | 2 +-
> kernel/bpf/arraymap.c | 8 ++++----
> kernel/bpf/core.c | 2 +-
> kernel/bpf/trampoline.c | 12 ++++++------
> 8 files changed, 32 insertions(+), 27 deletions(-)
>
> diff --git a/arch/arm64/net/bpf_jit_comp.c b/arch/arm64/net/bpf_jit_comp.c
> index 7d4af64e3982..b52549d18730 100644
> --- a/arch/arm64/net/bpf_jit_comp.c
> +++ b/arch/arm64/net/bpf_jit_comp.c
> @@ -2167,7 +2167,8 @@ static int gen_branch_or_nop(enum aarch64_insn_branch_type type, void *ip,
> * locations during the patching process, making the patching process easier.
> */
> int bpf_arch_text_poke(void *ip, enum bpf_text_poke_type poke_type,
> - void *old_addr, void *new_addr)
> + void *old_addr, void *new_addr,
[..]
> + bool checkip __maybe_unused)
Any idea why only riscv and x86 do this check?
Asking because maybe it makes sense to move this check into some
new generic bpf_text_poke and call it in the places where you currently
call checkip=true (and keep using bpf_arch_text_poke for checkip=false
case).
(don't see any issues with the current approach btw, just interested..)
next prev parent reply other threads:[~2023-11-28 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 9:28 [PATCHv2 bpf 0/2] bpf: Fix prog_array_map_poke_run map poke update Jiri Olsa
2023-11-28 9:28 ` [PATCHv2 bpf 1/2] bpf: Add checkip argument to bpf_arch_text_poke Jiri Olsa
2023-11-28 21:24 ` Stanislav Fomichev [this message]
2023-11-29 14:05 ` Jiri Olsa
2023-11-29 14:55 ` Jiri Olsa
2023-11-29 18:10 ` Stanislav Fomichev
2023-12-01 9:10 ` Jiri Olsa
2023-12-01 14:36 ` Ilya Leoshkevich
2023-12-03 20:50 ` Jiri Olsa
2023-11-28 9:28 ` [PATCHv2 bpf 2/2] bpf: Fix prog_array_map_poke_run map poke update Jiri Olsa
2023-11-28 22:44 ` [PATCHv2 bpf 0/2] " Ilya Leoshkevich
2023-11-29 13:23 ` Jiri Olsa
2023-12-01 13:13 ` Jiri Olsa
2023-12-01 14:31 ` Ilya Leoshkevich
2023-12-01 14:52 ` Jiri Olsa
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=ZWZafkt97qhgHynh@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=lee@kernel.org \
--cc=nathan@kernel.org \
--cc=pulehui@huawei.com \
--cc=songliubraving@fb.com \
--cc=will@kernel.org \
--cc=xukuohai@huawei.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox