From: Jiri Olsa <olsajiri@gmail.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Andrii Nakryiko <andrii.nakryiko@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>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Peter Zijlstra <peterz@infradead.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Subject: Re: [PATCHv2 bpf-next 6/6] selftests/bpf: Fix get_func_ip offset test for CONFIG_X86_KERNEL_IBT
Date: Tue, 16 Aug 2022 12:18:42 +0200 [thread overview]
Message-ID: <YvtvAkcnsrho+Xeq@krava> (raw)
In-Reply-To: <YvtAhPyiWDbTzCdA@krava>
On Tue, Aug 16, 2022 at 09:00:20AM +0200, Jiri Olsa wrote:
> On Mon, Aug 15, 2022 at 08:25:51PM -0700, Andrii Nakryiko wrote:
> > On Thu, Aug 11, 2022 at 2:16 AM Jiri Olsa <jolsa@kernel.org> wrote:
> > >
> > > With CONFIG_X86_KERNEL_IBT enabled the test for kprobe with offset
> > > won't work because of the extra endbr instruction.
> > >
> > > As suggested by Andrii adding CONFIG_X86_KERNEL_IBT detection
> > > and using appropriate offset value based on that.
> > >
> > > Also removing test7 program, because it does the same as test6.
> > >
> > > Suggested-by: Andrii Nakryiko <andrii@kernel.org>
> > > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > > ---
> > > .../bpf/prog_tests/get_func_ip_test.c | 62 +++++++++++++++----
> > > .../selftests/bpf/progs/get_func_ip_test.c | 20 +++---
> > > 2 files changed, 60 insertions(+), 22 deletions(-)
> > >
> > > diff --git a/tools/testing/selftests/bpf/prog_tests/get_func_ip_test.c b/tools/testing/selftests/bpf/prog_tests/get_func_ip_test.c
> > > index 938dbd4d7c2f..a4dab2fa2258 100644
> > > --- a/tools/testing/selftests/bpf/prog_tests/get_func_ip_test.c
> > > +++ b/tools/testing/selftests/bpf/prog_tests/get_func_ip_test.c
> > > @@ -2,7 +2,9 @@
> > > #include <test_progs.h>
> > > #include "get_func_ip_test.skel.h"
> > >
> > > -void test_get_func_ip_test(void)
> > > +static int config_ibt;
> > > +
> > > +static void test_function_entry(void)
> > > {
> > > struct get_func_ip_test *skel = NULL;
> > > int err, prog_fd;
> > > @@ -12,14 +14,6 @@ void test_get_func_ip_test(void)
> > > if (!ASSERT_OK_PTR(skel, "get_func_ip_test__open"))
> > > return;
> > >
> > > - /* test6 is x86_64 specifc because of the instruction
> > > - * offset, disabling it for all other archs
> > > - */
> > > -#ifndef __x86_64__
> > > - bpf_program__set_autoload(skel->progs.test6, false);
> > > - bpf_program__set_autoload(skel->progs.test7, false);
> > > -#endif
> > > -
> > > err = get_func_ip_test__load(skel);
> > > if (!ASSERT_OK(err, "get_func_ip_test__load"))
> > > goto cleanup;
> > > @@ -38,16 +32,62 @@ void test_get_func_ip_test(void)
> > >
> > > ASSERT_OK(err, "test_run");
> > >
> > > + config_ibt = skel->bss->config_ibt;
> >
> > skel->bss->config_ibt isn't actually necessary, you can just check
> > skel->kconfig->CONFIG_X86_KERNEL_IBT directly. And you won't need to
> > trigger BPF program unnecessary, libbpf will fill out kconfig section
> > during object/skeleton load phase.
>
> nice, did not know that ;-) will remove it
actually.. to get kconfig datasec generated in BTF the CONFIG_X86_KERNEL_IBT
symbol needs to be used.. so I came up with adding unused function:
int unused(void)
{
return CONFIG_X86_KERNEL_IBT ? 0 : 1;
}
but I wonder having the config_ibt variable is better and more clear
thoughts?
thanks,
jirka
next prev parent reply other threads:[~2022-08-16 11:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 9:15 [PATCHv2 bpf-next 0/6] bpf: Fixes for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-08-11 9:15 ` [PATCHv2 bpf-next 1/6] kprobes: Add new KPROBE_FLAG_ON_FUNC_ENTRY kprobe flag Jiri Olsa
2022-08-15 9:57 ` Peter Zijlstra
2022-08-15 10:10 ` Jiri Olsa
2022-08-15 12:40 ` Peter Zijlstra
2022-08-16 7:01 ` Jiri Olsa
2022-08-30 15:08 ` Jiri Olsa
2022-09-08 8:26 ` Jiri Olsa
2022-09-08 12:01 ` Masami Hiramatsu
2022-08-11 9:15 ` [PATCHv2 bpf-next 2/6] ftrace: Keep the resolved addr in kallsyms_callback Jiri Olsa
2022-08-15 10:13 ` Peter Zijlstra
2022-08-15 10:30 ` Jiri Olsa
2022-08-15 12:45 ` Peter Zijlstra
2022-08-16 7:06 ` Jiri Olsa
2022-09-08 12:35 ` Masami Hiramatsu
2022-09-08 19:41 ` Jiri Olsa
2022-08-11 9:15 ` [PATCHv2 bpf-next 3/6] bpf: Use given function address for trampoline ip arg Jiri Olsa
2022-08-15 10:18 ` Peter Zijlstra
2022-08-15 10:57 ` Jiri Olsa
2022-08-15 12:51 ` Peter Zijlstra
2022-08-17 13:40 ` Jiri Olsa
2022-08-11 9:15 ` [PATCHv2 bpf-next 4/6] bpf: Adjust kprobe_multi entry_ip for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-08-11 9:15 ` [PATCHv2 bpf-next 5/6] bpf: Return value in kprobe get_func_ip only for entry address Jiri Olsa
2022-08-11 9:15 ` [PATCHv2 bpf-next 6/6] selftests/bpf: Fix get_func_ip offset test for CONFIG_X86_KERNEL_IBT Jiri Olsa
2022-08-16 3:25 ` Andrii Nakryiko
2022-08-16 7:00 ` Jiri Olsa
2022-08-16 10:18 ` Jiri Olsa [this message]
2022-08-16 17:28 ` Andrii Nakryiko
2022-08-16 17:19 ` Andrii Nakryiko
2022-08-16 3:27 ` [PATCHv2 bpf-next 0/6] bpf: Fixes " Andrii Nakryiko
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=YvtvAkcnsrho+Xeq@krava \
--to=olsajiri@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.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