From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev
Subject: Re: [PATCH bpf-next] selftests/bpf: Add additional mprog query test coverage
Date: Tue, 17 Oct 2023 20:00:24 +0000 [thread overview]
Message-ID: <169757282416.23069.14344116792289833086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231017081728.24769-1-daniel@iogearbox.net>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 17 Oct 2023 10:17:28 +0200 you wrote:
> Add several new test cases which assert corner cases on the mprog query
> mechanism, for example, around passing in a too small or a larger array
> than the current count.
>
> ./test_progs -t tc_opts
> #252 tc_opts_after:OK
> #253 tc_opts_append:OK
> #254 tc_opts_basic:OK
> #255 tc_opts_before:OK
> #256 tc_opts_chain_classic:OK
> #257 tc_opts_chain_mixed:OK
> #258 tc_opts_delete_empty:OK
> #259 tc_opts_demixed:OK
> #260 tc_opts_detach:OK
> #261 tc_opts_detach_after:OK
> #262 tc_opts_detach_before:OK
> #263 tc_opts_dev_cleanup:OK
> #264 tc_opts_invalid:OK
> #265 tc_opts_max:OK
> #266 tc_opts_mixed:OK
> #267 tc_opts_prepend:OK
> #268 tc_opts_query:OK
> #269 tc_opts_query_attach:OK
> #270 tc_opts_replace:OK
> #271 tc_opts_revision:OK
> Summary: 20/0 PASSED, 0 SKIPPED, 0 FAILED
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Add additional mprog query test coverage
https://git.kernel.org/bpf/bpf-next/c/24516309e330
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-17 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 8:17 [PATCH bpf-next] selftests/bpf: Add additional mprog query test coverage Daniel Borkmann
2023-10-17 9:09 ` Alan Maguire
2023-10-17 20:00 ` patchwork-bot+netdevbpf [this message]
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=169757282416.23069.14344116792289833086.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@linux.dev \
/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