BPF List
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Stanislav Fomichev <sdf@google.com>
Cc: "Jiri Olsa" <olsajiri@gmail.com>,
	"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: Fri, 1 Dec 2023 10:10:18 +0100	[thread overview]
Message-ID: <ZWmi-mMYqH_0n4av@krava> (raw)
In-Reply-To: <CAKH8qBuz4XGfg+w7oitF9p_kW-+ycgwEoUTF8vw36u1-A_qnLg@mail.gmail.com>

On Wed, Nov 29, 2023 at 10:10:22AM -0800, Stanislav Fomichev wrote:
> On Wed, Nov 29, 2023 at 6:55 AM Jiri Olsa <olsajiri@gmail.com> wrote:
> >
> > On Wed, Nov 29, 2023 at 03:05:21PM +0100, Jiri Olsa wrote:
> > > On Tue, Nov 28, 2023 at 01:24:14PM -0800, Stanislav Fomichev wrote:
> > > > 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?
> > >
> > > so arm does the check as well, but needs the data from the lookup
> > > to patch things properly.. but IIUC it does not suffer the same
> > > issue because it does not implement direct tail calls [1] which
> > > is used only on x86
> > >
> > > >
> > > > 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..)
> > >
> > > I tried to add new function for that, but it did not look good for arm
> > > because it needs to do the lookup anyway
> > >
> > > hm maybe we could use new arch function that would cover the single
> > > tail call 'text poke' update in prog_array_map_poke_run and would be
> > > implemented only on x86 ... using __bpf_arch_text_poke directly
> >
> > looks like below change would be enough, I'll test and send new version
> 
> sg. I'm still not 100% sure why it's x86 only, I was (probably
> wrongly?) assuming that at least arm64 jit is mostly on par with x86
> :-)

AFAICS the direct tail calls are on x86, CI also seems to be ok with
that change.. I'll send it as formal patch

jirka

  reply	other threads:[~2023-12-01  9:10 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
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 [this message]
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=ZWmi-mMYqH_0n4av@krava \
    --to=olsajiri@gmail.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=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=lee@kernel.org \
    --cc=nathan@kernel.org \
    --cc=pulehui@huawei.com \
    --cc=sdf@google.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