From: Krister Johansen <kjlx@templeofstupid.com>
To: Yonghong Song <yhs@meta.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf v3 2/2] selftests/bpf: add a test for subprogram extables
Date: Fri, 9 Jun 2023 14:34:04 -0700 [thread overview]
Message-ID: <20230609213404.GB2012@templeofstupid.com> (raw)
In-Reply-To: <49a8216a-4333-a044-ceea-c59980913966@meta.com>
On Thu, Jun 08, 2023 at 08:52:36PM -0700, Yonghong Song wrote:
> On 6/8/23 5:11 PM, Krister Johansen wrote:
> > In certain situations a program with subprograms may have a NULL
> > extable entry. This should not happen, and when it does, it turns a
> > single trap into multiple. Add a test case for further debugging and to
> > prevent regressions. N.b: without any other patches this can panic or
> > oops a kernel.
>
> It would be great if you can add the panic call stack in the commit message.
>
> Please also mention that three identical bpf programs in the test
> significantly increased the 'oops' chance. Just one program may
> not be able to trigger the issue.
Apologies, I mistakenly put the oops in the cover letter when you did tell
me to put it in the commit message for this patch. That is fixed now.
> > Signed-off-by: Krister Johansen <kjlx@templeofstupid.com>
> > ---
> > .../bpf/prog_tests/subprogs_extable.c | 31 +++++++++++++
> > .../bpf/progs/test_subprogs_extable.c | 46 +++++++++++++++++++
> > 2 files changed, 77 insertions(+)
> > create mode 100644 tools/testing/selftests/bpf/prog_tests/subprogs_extable.c
> > create mode 100644 tools/testing/selftests/bpf/progs/test_subprogs_extable.c
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/subprogs_extable.c b/tools/testing/selftests/bpf/prog_tests/subprogs_extable.c
> > new file mode 100644
> > index 000000000000..2201988274a4
> > --- /dev/null
> > +++ b/tools/testing/selftests/bpf/prog_tests/subprogs_extable.c
> > @@ -0,0 +1,31 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +#include <test_progs.h>
> > +#include "test_subprogs_extable.skel.h"
> > +
> > +void test_subprogs_extable(void)
> > +{
> > + const int READ_SZ = 456;
>
> There is no need to use uppercase for READ_SZ.
> Just do
> const int read_sz = 456;
> is sufficient.
>
> > + struct test_subprogs_extable *skel;
> > + int err;
> > +
> > + skel = test_subprogs_extable__open();
> > + if (!ASSERT_OK_PTR(skel, "skel_open"))
> > + return;
> > +
> > + err = test_subprogs_extable__load(skel);
> > + if (!ASSERT_OK(err, "skel_load"))
> > + goto cleanup;
>
> You can combine the above open and load with a single one
> test_subprogs_extable__open_and_load().
>
> > +
> > + err = test_subprogs_extable__attach(skel);
> > + if (!ASSERT_OK(err, "skel_attach"))
> > + goto cleanup;
> > +
> > + /* trigger tracepoint */
> > + ASSERT_OK(trigger_module_test_read(READ_SZ), "trigger_read");
>
> I think we should at least ensure that the program is triggered. For
> example, add a global variable 'triggered' in the program and
> triggered will be set to 1 in the program if the program is running.
> Here check
> skel->bss->triggered
> must be 1.
Thanks for the additional feedback on cleaning this up. I've
incorporated the requested changes and will send out a v4 shortly.
-K
next prev parent reply other threads:[~2023-06-09 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 0:10 [PATCH bpf v3 0/2] bpf: fix NULL dereference during extable search Krister Johansen
2023-06-09 0:10 ` [PATCH bpf v3 1/2] bpf: ensure main program has an extable Krister Johansen
2023-06-09 3:33 ` Yonghong Song
2023-06-09 0:11 ` [PATCH bpf v3 2/2] selftests/bpf: add a test for subprogram extables Krister Johansen
2023-06-09 3:52 ` Yonghong Song
2023-06-09 21:34 ` Krister Johansen [this message]
2023-06-09 18:15 ` Alexei Starovoitov
2023-06-09 19:08 ` Krister Johansen
2023-06-12 13:46 ` Ilya Leoshkevich
2023-06-12 22:07 ` Alexei Starovoitov
2023-06-12 22:12 ` Krister Johansen
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=20230609213404.GB2012@templeofstupid.com \
--to=kjlx@templeofstupid.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=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yhs@meta.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