From: Jakub Sitnicki <jakub@cloudflare.com>
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: Shuah Khan <shuah@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@cloudflare.com, Martin KaFai Lau <kafai@fb.com>,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] selftests: bpf: fix detach from sockmap tests
Date: Thu, 09 Jul 2020 20:21:24 +0200 [thread overview]
Message-ID: <87eepka6sb.fsf@cloudflare.com> (raw)
In-Reply-To: <20200709115151.75829-1-lmb@cloudflare.com>
On Thu, Jul 09, 2020 at 01:51 PM CEST, Lorenz Bauer wrote:
> Fix sockmap tests which rely on old bpf_prog_dispatch behaviour.
> In the first case, the tests check that detaching without giving
> a program succeeds. Since these are not the desired semantics,
> invert the condition. In the second case, the clean up code doesn't
> supply the necessary program fds.
>
> Reported-by: Martin KaFai Lau <kafai@fb.com>
> Signed-off-by: Lorenz Bauer <lmb@cloudflare.com>
> Fixes: bb0de3131f4c ("bpf: sockmap: Require attach_bpf_fd when detaching a program")
> ---
> tools/testing/selftests/bpf/test_maps.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/test_maps.c b/tools/testing/selftests/bpf/test_maps.c
> index 6a12a0e01e07..754cf611723e 100644
> --- a/tools/testing/selftests/bpf/test_maps.c
> +++ b/tools/testing/selftests/bpf/test_maps.c
> @@ -789,19 +789,19 @@ static void test_sockmap(unsigned int tasks, void *data)
> }
>
> err = bpf_prog_detach(fd, BPF_SK_SKB_STREAM_PARSER);
> - if (err) {
> + if (!err) {
> printf("Failed empty parser prog detach\n");
> goto out_sockmap;
> }
>
> err = bpf_prog_detach(fd, BPF_SK_SKB_STREAM_VERDICT);
> - if (err) {
> + if (!err) {
> printf("Failed empty verdict prog detach\n");
> goto out_sockmap;
> }
>
> err = bpf_prog_detach(fd, BPF_SK_MSG_VERDICT);
> - if (err) {
> + if (!err) {
> printf("Failed empty msg verdict prog detach\n");
> goto out_sockmap;
> }
> @@ -1090,19 +1090,19 @@ static void test_sockmap(unsigned int tasks, void *data)
> assert(status == 0);
> }
>
> - err = bpf_prog_detach(map_fd_rx, __MAX_BPF_ATTACH_TYPE);
> + err = bpf_prog_detach2(parse_prog, map_fd_rx, __MAX_BPF_ATTACH_TYPE);
> if (!err) {
> printf("Detached an invalid prog type.\n");
> goto out_sockmap;
> }
>
> - err = bpf_prog_detach(map_fd_rx, BPF_SK_SKB_STREAM_PARSER);
> + err = bpf_prog_detach2(parse_prog, map_fd_rx, BPF_SK_SKB_STREAM_PARSER);
> if (err) {
> printf("Failed parser prog detach\n");
> goto out_sockmap;
> }
>
> - err = bpf_prog_detach(map_fd_rx, BPF_SK_SKB_STREAM_VERDICT);
> + err = bpf_prog_detach2(verdict_prog, map_fd_rx, BPF_SK_SKB_STREAM_VERDICT);
> if (err) {
> printf("Failed parser prog detach\n");
> goto out_sockmap;
Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
next prev parent reply other threads:[~2020-07-09 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 11:51 [PATCH bpf] selftests: bpf: fix detach from sockmap tests Lorenz Bauer
2020-07-09 18:21 ` Jakub Sitnicki [this message]
2020-07-09 21:43 ` Daniel Borkmann
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=87eepka6sb.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).