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: <CAADnVQK82PRjGnw+wht4ZpxK3s3St2qWRoO6bJbuY3cARXXPxQ@mail.gmail.com> Date: Fri, 29 Sep 2023 12:25:17 -0700 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: Daniel Borkmann <daniel@...earbox.net> Cc: Toke Høiland-Jørgensen <toke@...nel.org>, bpf <bpf@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, Martin KaFai Lau <martin.lau@...nel.org>, Nikolay Aleksandrov <razor@...ckwall.org>, Alexei Starovoitov <ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>, John Fastabend <john.fastabend@...il.com> Subject: Re: [PATCH bpf-next 1/8] meta, bpf: Add bpf programmable meta device On Thu, Sep 28, 2023 at 2:14 PM Daniel Borkmann <daniel@...earbox.net> wrote: > > > > I think we should just name the driver 'bpfnet'; it's not pretty, but > > it's obvious and descriptive. Optionally we could teach 'ip' to > > understand just 'bpf' as the device type, so you could go 'ip link add > > type bpf' and get one of these. > > I'll think about it, the bpfnet sounds terrible as you also noticed. I > definitely don't like that. Perhaps meta_net as suggested by Andrii in > the other thread could be a compromise. Need to sleep over it, my pref > was actually to keep it shorter. I don't like the meta name either standalone or as meta_net. Maybe "hollow" or "void" netdevice? Since this netdev doesn't have a substance when bpf prog is not attached. It's empty == dummy == hollow == void netdevice.
Powered by blists - more mailing lists