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
| ||
|
Message-ID: <19cd3d0a-12eb-b8ca-a054-62d86ba2a509@gmail.com> Date: Tue, 30 May 2017 18:35:37 -0600 From: David Ahern <dsahern@...il.com> To: Martin KaFai Lau <kafai@...com>, netdev@...r.kernel.org Cc: Alexei Starovoitov <ast@...com>, Daniel Borkmann <daniel@...earbox.net>, kernel-team@...com Subject: Re: [PATCH net-next 0/8] Introduce bpf ID On 5/30/17 6:08 PM, Martin KaFai Lau wrote: > This patch series: > 1) Introduce ID for both bpf_prog and bpf_map. > 2) Add bpf commands to iterate the prog IDs and map > IDs of the system. > 3) Add bpf commands to get a prog/map fd from an ID > 4) Add bpf command to get prog/map info from a fd. > The prog/map info is a jump start in this patchset > and it is not meant to be a complete list. They can > be extended in the future patches. Interesting. This really simplifies the bpf retrieval I have been working on: https://github.com/dsahern/linux/commits/bpf/retrieve-bpf-wip Having the net device, filter, route, socket, cgroup, etc return the ids for attached programs solves the problem of getting a reference to all of the places BPF programs can be placed. This patch set turns an id into a fd, and my patches allow the fd to be used to get the bpf code.
Powered by blists - more mailing lists