netdev - Re: [PATCH bpf-next] libbpf: reduce log level for custom section names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAADnVQJtDHv4r28Skdy1Dt8i7iMareiMz-+3O8M=1gGEG3-4GQ@mail.gmail.com>
Date:   Tue, 17 Dec 2019 18:41:21 -0800
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Andrii Nakryiko <andriin@...com>
Cc:     bpf <bpf@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next] libbpf: reduce log level for custom section names

On Tue, Dec 17, 2019 at 3:42 PM Andrii Nakryiko <andriin@...com> wrote:
>
> Libbpf is trying to recognize BPF program type based on its section name
> during bpf_object__open() phase. This is not strictly enforced and user code
> has ability to specify/override correct BPF program type after open.  But if
> BPF program is using custom section name, libbpf will still emit warnings,
> which can be quite annoying to users. This patch reduces log level of
> information messages emitted by libbpf if section name is not canonical. User
> can still get a list of all supported section names as debug-level message.
>
> Signed-off-by: Andrii Nakryiko <andriin@...com>

Applied. Thanks

selftests/bpf/ build looks very nice now.