bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kui-Feng Lee <sinquersw@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>,
	Kui-Feng Lee <thinker.li@gmail.com>,
	bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
	song@kernel.org, kernel-team@meta.com, andrii@kernel.org
Cc: kuifeng@meta.com
Subject: Re: [PATCH bpf-next v3 3/7] bpf: create repeated fields for arrays.
Date: Fri, 3 May 2024 11:02:38 -0700	[thread overview]
Message-ID: <0fba228d-ee81-4aee-901f-c60dfd53c102@gmail.com> (raw)
In-Reply-To: <017ecee002197526aa5d91d856c25510d36b57ce.camel@gmail.com>



On 5/2/24 10:20, Eduard Zingerman wrote:
> On Wed, 2024-05-01 at 13:47 -0700, Kui-Feng Lee wrote:
> 
> I think this looks good for repeating fields of nested arrays
> (w/o visiting nested structures), two nits below.
> 
>> @@ -3575,6 +3628,19 @@ static int btf_find_datasec_var(const struct btf *btf, const struct btf_type *t,
>>   	for_each_vsi(i, t, vsi) {
>>   		const struct btf_type *var = btf_type_by_id(btf, vsi->type);
>>   		const struct btf_type *var_type = btf_type_by_id(btf, var->type);
>> +		const struct btf_array *array;
>> +		u32 j, nelems = 1;
>> +
>> +		/* Walk into array types to find the element type and the
>> +		 * number of elements in the (flattened) array.
>> +		 */
>> +		for (j = 0; j < MAX_RESOLVE_DEPTH && btf_type_is_array(var_type); j++) {
>> +			array = btf_array(var_type);
>> +			nelems *= array->nelems;
>> +			var_type = btf_type_by_id(btf, array->type);
>> +		}
>> +		if (nelems == 0)
>> +			continue;
> 
> Nit: Should this return an error if j == MAX_RESOLVE_DEPTH after the loop?

agree


> 
>>   
>>   		field_type = btf_get_field_type(__btf_name_by_offset(btf, var_type->name_off),
>>   						field_mask, &seen_mask, &align, &sz);
>> @@ -3584,7 +3650,7 @@ static int btf_find_datasec_var(const struct btf *btf, const struct btf_type *t,
>>   			return field_type;
>>   
>>   		off = vsi->offset;
>> -		if (vsi->size != sz)
>> +		if (vsi->size != sz * nelems)
>>   			continue;
>>   		if (off % align)
>>   			continue;
>> @@ -3624,9 +3690,14 @@ static int btf_find_datasec_var(const struct btf *btf, const struct btf_type *t,
>>   
>>   		if (ret == BTF_FIELD_IGNORE)
>>   			continue;
>> -		if (idx >= info_cnt)
>> +		if (idx + nelems > info_cnt)
>>   			return -E2BIG;
> 
> Nit: This is bounded by BTF_FIELDS_MAX which has value of 11,
>       would that be enough?

So far, no one has complained it yet!
But, some one will reach the limit in future.
If people want a flexible length, I will solve it in a follow-up.
WDYT?

> 
>> -		++idx;
>> +		if (nelems > 1) {
>> +			ret = btf_repeat_field(info, idx, nelems - 1, sz);
>> +			if (ret < 0)
>> +				return ret;
>> +		}
>> +		idx += nelems;
>>   	}
>>   	return idx;
>>   }
> 
> 

  reply	other threads:[~2024-05-03 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 20:47 [PATCH bpf-next v3 0/7] Enable BPF programs to declare arrays of kptr, bpf_rb_root, and bpf_list_head Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 1/7] bpf: Remove unnecessary checks on the offset of btf_field Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 2/7] bpf: Remove unnecessary call to btf_field_type_size() Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 3/7] bpf: create repeated fields for arrays Kui-Feng Lee
2024-05-02 17:20   ` Eduard Zingerman
2024-05-03 18:02     ` Kui-Feng Lee [this message]
2024-05-03 18:10       ` Eduard Zingerman
2024-05-01 20:47 ` [PATCH bpf-next v3 4/7] bpf: look into the types of the fields of a struct type recursively Kui-Feng Lee
2024-05-02 19:34   ` Eduard Zingerman
2024-05-03 18:07     ` Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 5/7] selftests/bpf: Test kptr arrays and kptrs in nested struct fields Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 6/7] selftests/bpf: Test global bpf_rb_root arrays and fields in nested struct types Kui-Feng Lee
2024-05-01 20:47 ` [PATCH bpf-next v3 7/7] selftests/bpf: Test global bpf_list_head arrays Kui-Feng Lee

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=0fba228d-ee81-4aee-901f-c60dfd53c102@gmail.com \
    --to=sinquersw@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=kuifeng@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=song@kernel.org \
    --cc=thinker.li@gmail.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;
as well as URLs for NNTP newsgroup(s).