public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "zhudi (E)" <zhudi2@huawei.com>
To: Yonghong Song <yhs@fb.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"ast@kernel.org" <ast@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	"andrii@kernel.org" <andrii@kernel.org>,
	"kafai@fb.com" <kafai@fb.com>,
	"songliubraving@fb.com" <songliubraving@fb.com>,
	"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
	"kpsingh@kernel.org" <kpsingh@kernel.org>,
	"jakub@cloudflare.com" <jakub@cloudflare.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v5 2/2] selftests: bpf: test BPF_PROG_QUERY for progs attached to sockmap
Date: Thu, 4 Nov 2021 06:09:19 +0000	[thread overview]
Message-ID: <3e98a5f5cd9a482fa95acc052484914d@huawei.com> (raw)

> On 11/3/21 6:07 PM, Di Zhu wrote:
> > Add test for querying progs attached to sockmap. we use an existing
> > libbpf query interface to query prog cnt before and after progs
> > attaching to sockmap and check whether the queried prog id is right.
> >
> > Signed-off-by: Di Zhu <zhudi2@huawei.com>
> > ---
> >   .../selftests/bpf/prog_tests/sockmap_basic.c  | 75 +++++++++++++++++++
> >   .../bpf/progs/test_sockmap_progs_query.c      | 24 ++++++
> >   2 files changed, 99 insertions(+)
> >   create mode 100644
> tools/testing/selftests/bpf/progs/test_sockmap_progs_query.c
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> b/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> > index 1352ec104149..de8f91d91240 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> > @@ -8,6 +8,7 @@
> >   #include "test_sockmap_update.skel.h"
> >   #include "test_sockmap_invalid_update.skel.h"
> >   #include "test_sockmap_skb_verdict_attach.skel.h"
> > +#include "test_sockmap_progs_query.skel.h"
> >   #include "bpf_iter_sockmap.skel.h"
> >
> >   #define TCP_REPAIR		19	/* TCP sock is under repair right now */
> > @@ -315,6 +316,74 @@ static void test_sockmap_skb_verdict_attach(enum
> bpf_attach_type first,
> >   	test_sockmap_skb_verdict_attach__destroy(skel);
> >   }
> >
> > +static __u32 query_prog_id(int prog_fd)
> > +{
> > +	struct bpf_prog_info info = {};
> > +	__u32 info_len = sizeof(info);
> > +	int err;
> > +
> > +	err = bpf_obj_get_info_by_fd(prog_fd, &info, &info_len);
> > +	if (CHECK_FAIL(err || info_len != sizeof(info))) {
> > +		perror("bpf_obj_get_info_by_fd");
> 
> Please use ASSERT_* macros. These macros are defined in test_progs.h.
> We may have some old files still using CHECK* which are not converted
> to ASSERT* yet. But for new contributions, we would like to use
> ASSERT* from start. You can check other prog_tests/*.c files for
> examples.
> 
> For the above example, you can do
> 	if (!ASSERT_OK(err, "bpf_obj_get_info_by_fd") ||
> 	    !ASSERT_EQ(info_len, sizeof(info), "bpf_obj_get_info_by_fd"))
> 		return 0;

I refer to the implementation of the old codes, I will modify it
Thanks,


> > +		return 0;
> > +	}
> > +
> > +	return info.id;
> [...]
> > +	err = bpf_prog_query(map_fd, attach_type, 0 /* query flags */,
> > +			     &attach_flags, prog_ids, &prog_cnt);
> > +	if (CHECK(err, "bpf_prog_query", "failed\n"))
> > +		goto out;
> 
> In this case, you can use
> 	if (!ASSERT_OK(err, "bpf_prog_query"))
> 		goto out;
> 
> Please also change below other CHECK usages.
> 
> > +
> > +	if (CHECK(attach_flags != 0, "bpf_prog_query",
> > +		  "wrong attach_flags on query: %u", attach_flags))
> > +		goto out;
> > +
> > +	if (CHECK(prog_cnt != 0, "bpf_prog_query",
> > +		  "wrong program count on query: %u", prog_cnt))
> > +		goto out;
> > +
> > +	err = bpf_prog_attach(verdict_fd, map_fd, attach_type, 0);
> > +	if (CHECK(err, "bpf_prog_attach", "failed\n"))
> > +		goto out;
> > +
> > +	prog_cnt = 1;
> > +	err = bpf_prog_query(map_fd, attach_type, 0 /* query flags */,
> > +			     &attach_flags, prog_ids, &prog_cnt);
> > +
> > +	CHECK(err, "bpf_prog_query", "failed\n");
> > +	CHECK(attach_flags != 0, "bpf_prog_query attach_flags",
> > +	      "wrong attach_flags on query: %u", attach_flags);
> > +	CHECK(prog_cnt != 1, "bpf_prog_query prog_cnt",
> > +	      "wrong program count on query: %u", prog_cnt);
> > +	CHECK(prog_ids[0] != query_prog_id(verdict_fd), "bpf_prog_query",
> > +	      "wrong prog_ids on query: %u", prog_ids[0]);
> [...]

             reply	other threads:[~2021-11-04  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  6:09 zhudi (E) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-17  2:59 [PATCH bpf-next v5 2/2] selftests: bpf: test BPF_PROG_QUERY for progs attached to sockmap zhudi (E)
2022-01-15  2:34 zhudi (E)
2022-01-15  2:48 ` Andrii Nakryiko
2022-01-13  9:00 [PATCH bpf-next v5 1/2] bpf: support " Di Zhu
2022-01-13  9:00 ` [PATCH bpf-next v5 2/2] selftests: bpf: test " Di Zhu
2022-01-15  1:18   ` Andrii Nakryiko
2021-11-05  1:57 [PATCH bpf-next v5 1/2] bpf: support " Di Zhu
2021-11-05  1:57 ` [PATCH bpf-next v5 2/2] selftests: bpf: test " Di Zhu
2021-11-05  4:24   ` Yonghong Song
2021-11-04  1:07 [PATCH bpf-next v5 1/2] bpf: support " Di Zhu
2021-11-04  1:07 ` [PATCH bpf-next v5 2/2] selftests: bpf: test " Di Zhu
2021-11-04  5:51   ` Yonghong Song

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=3e98a5f5cd9a482fa95acc052484914d@huawei.com \
    --to=zhudi2@huawei.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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