From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com
Subject: Re: [RFC bpf-next 1/5] selftests/bpf: support custom per-test flags and multiple expected messages
Date: Wed, 01 Mar 2023 00:30:19 +0200 [thread overview]
Message-ID: <06e29b322d777c30fe9b163f9d13f11503a303d9.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzZ-9iHzotYj2K3a+USFsxmqLEA+pHm4Ot6Nr2WtZ-AHeA@mail.gmail.com>
On Tue, 2023-02-28 at 10:53 -0800, Andrii Nakryiko wrote:
> On Mon, Jan 23, 2023 at 6:52 AM Eduard Zingerman <eddyz87@gmail.com> wrote:
> >
> > From: Andrii Nakryiko <andrii@kernel.org>
> >
> > Extend __flag attribute by allowing to specify one of the following:
> > * BPF_F_STRICT_ALIGNMENT
> > * BPF_F_ANY_ALIGNMENT
> > * BPF_F_TEST_RND_HI32
> > * BPF_F_TEST_STATE_FREQ
> > * BPF_F_SLEEPABLE
> > * BPF_F_XDP_HAS_FRAGS
> > * Some numeric value
> >
> > Extend __msg attribute by allowing to specify multiple exepcted messages.
> > All messages are expected to be present in the verifier log in the
> > order of application.
> >
> > Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> > [ Eduard: added commit message, formatting ]
> > Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
> > ---
>
> hey Eduard,
>
> When you get a chance, can you please send this patch separately from
> the rest of the test_verifier rework patch set (it probably makes
> sense to also add #define __flags in this patch as well, given you are
> parsing its definition in this patch).
>
> This would great help me with my work that uses all this
> assembly-level test facilities. Thanks!
Hi Andrii,
Rebase didn't change anything in the patch, I added __flags macro,
some some comments, and started the CI job: [1].
Feels weird to post it, tbh, because it's 100% your code w/o added
value from my side.
Thanks,
Eduard
[1] https://github.com/kernel-patches/bpf/pull/4688
>
>
>
> > tools/testing/selftests/bpf/test_loader.c | 69 ++++++++++++++++++++---
> > tools/testing/selftests/bpf/test_progs.h | 1 +
> > 2 files changed, 61 insertions(+), 9 deletions(-)
> >
> > diff --git a/tools/testing/selftests/bpf/test_loader.c b/tools/testing/selftests/bpf/test_loader.c
> > index 679efb3aa785..bf41390157bf 100644
> > --- a/tools/testing/selftests/bpf/test_loader.c
> > +++ b/tools/testing/selftests/bpf/test_loader.c
> > @@ -13,12 +13,15 @@
> > #define TEST_TAG_EXPECT_SUCCESS "comment:test_expect_success"
> > #define TEST_TAG_EXPECT_MSG_PFX "comment:test_expect_msg="
> > #define TEST_TAG_LOG_LEVEL_PFX "comment:test_log_level="
> > +#define TEST_TAG_PROG_FLAGS_PFX "comment:test_prog_flags="
> >
>
> [...]
next prev parent reply other threads:[~2023-02-28 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 14:51 [RFC bpf-next 0/5] test_verifier tests migration to inline assembly Eduard Zingerman
2023-01-23 14:51 ` [RFC bpf-next 1/5] selftests/bpf: support custom per-test flags and multiple expected messages Eduard Zingerman
2023-02-28 18:53 ` Andrii Nakryiko
2023-02-28 22:30 ` Eduard Zingerman [this message]
2023-03-01 17:12 ` Andrii Nakryiko
2023-03-01 17:58 ` Eduard Zingerman
2023-01-23 14:51 ` [RFC bpf-next 2/5] selftests/bpf: unprivileged tests for test_loader.c Eduard Zingerman
2023-01-23 14:51 ` [RFC bpf-next 3/5] selftests/bpf: generate boilerplate code for test_loader-based tests Eduard Zingerman
2023-01-26 1:43 ` Andrii Nakryiko
2023-01-26 23:29 ` Eduard Zingerman
2023-01-23 14:51 ` [RFC bpf-next 4/5] selftests/bpf: __imm_insn macro to embed raw insns in inline asm Eduard Zingerman
2023-01-26 2:48 ` Andrii Nakryiko
2023-01-23 14:51 ` [RFC bpf-next 5/5] selftests/bpf: convert jeq_infer_not_null tests to inline assembly Eduard Zingerman
2023-01-26 1:33 ` [RFC bpf-next 0/5] test_verifier tests migration " Andrii Nakryiko
2023-01-26 3:25 ` Alexei Starovoitov
2023-01-27 0:43 ` Eduard Zingerman
2023-01-27 0:30 ` Eduard Zingerman
2023-01-27 17:41 ` 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=06e29b322d777c30fe9b163f9d13f11503a303d9.camel@gmail.com \
--to=eddyz87@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=kernel-team@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 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.