netdev - Re: [PATCH v2 net-next 0/8] Introduce bpf ID

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]

Date:   Thu, 1 Jun 2017 11:51:24 -0600
From:   David Ahern <dsahern@...il.com>
To:     Alexei Starovoitov <ast@...com>, Jakub Kicinski <kubakici@...pl>,
        Martin KaFai Lau <kafai@...com>,
        Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc:     netdev@...r.kernel.org, Daniel Borkmann <daniel@...earbox.net>,
        kernel-team@...com
Subject: Re: [PATCH v2 net-next 0/8] Introduce bpf ID

On 6/1/17 11:24 AM, Alexei Starovoitov wrote:
> 
> what problem are we trying to solve?
> If we don't agree on the problem, we won't be able to agree on the
> solution.

I want the ability to retrieve the BPF instructions pushed to the
kernel. Not just for cgroups and VRF, but everywhere - cgroups, sockets,
xdp, filters, etc. I have this stated many times, including to you at
netconf in April. From that discussion and the discussion on the RFC
patch I sent in February, I thought we had an agreement that saving the
instructions was the first step.

Quentin at 6wind has expressed a similar interest for cls_bpf and
act_bpf code.

I read Jakub's email as wanting the same but for XDP.

The patches I referenced earlier save the original instructions and
enable them to be read by userspace from an fd return by the bpf
syscall. Combine that with the ID and we have a solution.