netdev - Re: [RFC net-next 0/2] Introduce bpf

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: <e81805c8-0499-a0a5-b788-0168947d9b8c@stressinduktion.org>
Date:   Thu, 27 Apr 2017 15:36:59 +0200
From:   Hannes Frederic Sowa <hannes@...essinduktion.org>
To:     Martin KaFai Lau <kafai@...com>, netdev@...r.kernel.org
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        Alexei Starovoitov <ast@...com>, kernel-team@...com
Subject: Re: [RFC net-next 0/2] Introduce bpf_prog ID and iteration

On 27.04.2017 08:24, Martin KaFai Lau wrote:
> This patchset introduces the bpf_prog ID and a new bpf cmd to
> iterate all bpf_prog in the system.
> 
> It is still incomplete.  The idea can be extended to bpf_map.
> 
> Martin KaFai Lau (2):
>   bpf: Introduce bpf_prog ID
>   bpf: Test for bpf_prog ID and BPF_PROG_GET_NEXT_ID

Thanks Martin, I like the approach.

I think the progid is also much more suitable to be used in kallsyms
because it handles collisions correctly and let's correctly walk the
chain (for example imaging loading two identical programs but install
them at different hooks, kallsysms doesn't allow to find out which
program is installed where).

It would help a lot if you could pass the prog_id back during program
creation, otherwise it will be kind of difficult to get a hold on which
program is where. ;)

Thanks,
Hannes