netdev - Re: [RESEND][PATCH v3 bpf-next] btf: expose BTF info through sysfs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190813184536.GJ9280@kernel.org>
Date:   Tue, 13 Aug 2019 15:45:36 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Kernel Team <kernel-team@...com>
Subject: Re: [RESEND][PATCH v3 bpf-next] btf: expose BTF info through sysfs

Em Tue, Aug 13, 2019 at 11:08:14AM -0700, Andrii Nakryiko escreveu:
> On Tue, Aug 13, 2019 at 7:20 AM Daniel Borkmann <daniel@...earbox.net> wrote:
> > On 8/12/19 8:39 PM, Andrii Nakryiko wrote:
> > > 3. final vmlinux image is generated by linking this object file (and
> > >     kallsyms, if necessary). sysfs_btf.c then creates
> > >     /sys/kernel/btf/kernel file and exposes embedded BTF contents through
> > >     it. This allows, e.g., libbpf and bpftool access BTF info at
> > >     well-known location, without resorting to searching for vmlinux image
> > >     on disk (location of which is not standardized and vmlinux image
> > >     might not be even available in some scenarios, e.g., inside qemu
> > >     during testing).

> > Small question: given modules will be covered later, would it not be more
> > obvious to name it /sys/kernel/btf/vmlinux instead?
 
> vmlinux totally makes sense, not sure why I didn't think about that initially...

Agreed :-)
 
> I'll follow up with a rename.

Great.
 
 - Arnaldo