netdev - Re: prog ID and next steps. Was: [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]

Date:   Fri, 28 Apr 2017 20:57:08 +0200
From:   Hannes Frederic Sowa <hannes@...essinduktion.org>
To:     Daniel Borkmann <daniel@...earbox.net>,
        Alexei Starovoitov <ast@...com>,
        Martin KaFai Lau <kafai@...com>, netdev@...r.kernel.org
Cc:     kernel-team@...com, "David S. Miller" <davem@...emloft.net>,
        Jesper Dangaard Brouer <brouer@...hat.com>,
        John Fastabend <john.fastabend@...il.com>,
        Thomas Graf <tgraf@...g.ch>
Subject: Re: prog ID and next steps. Was: [RFC net-next 0/2] Introduce
 bpf_prog ID and iteration

On 28.04.2017 20:51, Hannes Frederic Sowa wrote:
> Doesn't this break if I have 2 mlx4 cards in the system with different
> XDP programs attached? I would have to add an additional parameter to
> one of the mlx4 functions to extract the net_device pointer to make the
> correlation then. Probably it will be much more difficult for other hooks.

Addendum:

I am referring to same XDP programs attached to two mlx4 NICs which use
different maps. It will be possible to correlate that with some more
advanced perf magic, if the driver passes suitable pointers around so
you can dereference the device name. Also, I am not sure where the
support for multi-rx-queue XDP is heading. It might be even more
difficult to understand it then.

Bye,
Hannes