Re: [PATCH bpf-next v2 0/6] Add support to emit verifier warnings

[Leon Hwang <hffilwlqm@gmail.com>]

On 18/4/26 19:06, Kumar Kartikeya Dwivedi wrote:
> On Wed, 8 Apr 2026 at 16:30, Leon Hwang <hffilwlqm@gmail.com> wrote:
>>
>> On 2026/4/8 22:55, Leon Hwang wrote:
>>>
[...]
>>>
>>> Since I'm going to add common attributes [1] support for BPF syscall,
>>> how about reporting the warnings via the common attributes? Even though,
>>> the original intent of common attributes support for BPF_LOAD was
>> BPF_LOAD -> BPF_PROG_LOAD
>>
>> Also, common attributes support for BPF_BTF_LOAD was to report logs,
>> similar to btf_log_* in union bpf_attr.
>>
>> If to report the warnings via common attributes for BPF_PROG_LOAD, we
>> should rethink the purpose of common attributes support for BPF_BTF_LOAD.
>>
>>> report the verifier log too.
>>>
>>> [1]
>> https://lore.kernel.org/bpf/20260216150445.68278-1-leon.hwang@linux.dev/
> 
> It can be used when present, I will switch to a warning bit in the log
> level in the next version. But I don't think we need to rethink
> anything. If we want warnings for other objects they can use the log
> level's warning bit to supply those to user space as well. When you
> add support you already have to figure out how to merge those in
> bpf_attr and common attributes.
> 
Make sense.

Thanks,
Leon