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: Thu, 7 Dec 2017 13:55:25 -0800 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: Roman Gushchin <guro@...com> Cc: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>, <kernel-team@...com>, <ast@...nel.org>, <daniel@...earbox.net>, <kafai@...com>, Quentin Monnet <quentin.monnet@...ronome.com>, David Ahern <dsahern@...il.com> Subject: Re: [PATCH v2 net-next 3/4] bpftool: implement prog load command On Thu, 7 Dec 2017 18:39:08 +0000, Roman Gushchin wrote: > Add the prog load command to load a bpf program from a specified > binary file and pin it to bpffs. > > Usage description and examples are given in the corresponding man > page. > > Syntax: > $ bpftool prog load SOURCE_FILE FILE > > FILE is a non-existing file on bpffs. > > Signed-off-by: Roman Gushchin <guro@...com> Reviewed-by: Jakub Kicinski <jakub.kicinski@...ronome.com> The only reservation I have is that SRC may confuse people, would it make sense to call the compiled code OBJ? I'm afraid someone may try to load a C source...
Powered by blists - more mailing lists