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
| ||
|
Date: Fri, 16 Oct 2015 19:43:08 -0700 From: Alexei Starovoitov <ast@...mgrid.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: Daniel Borkmann <daniel@...earbox.net>, Hannes Frederic Sowa <hannes@...essinduktion.org>, davem@...emloft.net, viro@...IV.linux.org.uk, tgraf@...g.ch, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Alexei Starovoitov <ast@...nel.org> Subject: Re: [PATCH net-next 3/4] bpf: add support for persistent maps/progs On 10/16/15 4:44 PM, Eric W. Biederman wrote: > Alexei Starovoitov <ast@...mgrid.com> writes: > >> We can argue about api for 2nd, whether it's mount with fd=1234 string >> or else, but for the first mount style doesn't make sense. > > Why does mount not make sense? It is exactly what you are looking for > so why does it not make sense? hmm, how do you get a new fd back after mounting it? Note, open cannot be overloaded, so we end up with BPF_NEW_FD anyway, but now it's more convoluted and empty mounts are everywhere. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists