BPF List
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@meta.com>
To: Eduard Zingerman <eddyz87@gmail.com>, Yonghong Song <yhs@fb.com>,
	bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Add a test where map key_type_id with decl_tag type
Date: Tue, 30 May 2023 10:48:50 -0700	[thread overview]
Message-ID: <f47eecae-a120-e079-b6a9-807c7480bb7b@meta.com> (raw)
In-Reply-To: <607940d5dd7515f65d24cd631e3946f50c573645.camel@gmail.com>



On 5/29/23 8:17 AM, Eduard Zingerman wrote:
> On Sat, 2023-05-27 at 15:31 -0700, Yonghong Song wrote:
>> Add a selftest where map creation key type_id is a decl_tag
>> pointing to a struct. Without previous patch, a kernel warning will
>> appear similar to the one in the previous patch. With the previous
>> patch, the kernel warning is silenced.
> 
> Looks good to me with a nitpick:
> commit message says "map creation key type_id is a decl_tag",
> but test case uses ".key_type_id = 1" which is INT
> and ".value_type_id = 3" which is DECL_TAG.
> 
> syscall.c:map_check_btf.c applies the same check both for key and value,
> maybe make two tests?

Sounds good. Will fix the commit message and add one more test so both
key and value are covered.

> 
>>
>> Signed-off-by: Yonghong Song <yhs@fb.com>
>> ---
>>   tools/testing/selftests/bpf/prog_tests/btf.c | 20 ++++++++++++++++++++
>>   1 file changed, 20 insertions(+)
>>
>> diff --git a/tools/testing/selftests/bpf/prog_tests/btf.c b/tools/testing/selftests/bpf/prog_tests/btf.c
>> index 210d643fda6c..69521e1dc330 100644
>> --- a/tools/testing/selftests/bpf/prog_tests/btf.c
>> +++ b/tools/testing/selftests/bpf/prog_tests/btf.c
>> @@ -3990,6 +3990,26 @@ static struct btf_raw_test raw_tests[] = {
>>   	.btf_load_err = true,
>>   	.err_str = "Invalid arg#1",
>>   },
>> +{
>> +	.descr = "decl_tag test #18, struct member, decl_tag as the value type",
>> +	.raw_types = {
>> +		BTF_TYPE_INT_ENC(0, BTF_INT_SIGNED, 0, 32, 4),	/* [1] */
>> +		BTF_STRUCT_ENC(0, 2, 8),			/* [2] */
>> +		BTF_MEMBER_ENC(NAME_TBD, 1, 0),
>> +		BTF_MEMBER_ENC(NAME_TBD, 1, 32),
>> +		BTF_DECL_TAG_ENC(NAME_TBD, 2, -1),		/* [3] */
>> +		BTF_END_RAW,
>> +	},
>> +	BTF_STR_SEC("\0m1\0m2\0tag"),
>> +	.map_type = BPF_MAP_TYPE_ARRAY,
>> +	.map_name = "tag_type_check_btf",
>> +	.key_size = sizeof(int),
>> +	.value_size = 8,
>> +	.key_type_id = 1,
>> +	.value_type_id = 3,
>> +	.max_entries = 1,
>> +	.map_create_err = true,
>> +},
>>   {
>>   	.descr = "type_tag test #1",
>>   	.raw_types = {
> 

      reply	other threads:[~2023-05-30 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 22:31 [PATCH bpf-next 1/2] bpf: Silence a warning in btf_type_id_size() Yonghong Song
2023-05-27 22:31 ` [PATCH bpf-next 2/2] selftests/bpf: Add a test where map key_type_id with decl_tag type Yonghong Song
2023-05-29 15:17   ` Eduard Zingerman
2023-05-30 17:48     ` Yonghong Song [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=f47eecae-a120-e079-b6a9-807c7480bb7b@meta.com \
    --to=yhs@meta.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --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