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: <20230503173348.703437-1-mtottenh@akamai.com> Date: Wed, 3 May 2023 13:33:48 -0400 From: Max Tottenham <mtottenh@...mai.com> To: <netdev@...r.kernel.org> CC: <johunt@...mai.com> Subject: [RFC PATCH iproute2] Add ability to specify eBPF pin path We have a use case where we have several different applications composed of sets of eBPF programs (programs that may be attached at the TC/XDP layers), that need to share maps and not conflict with each other. For XDP based programs, we are using the xdp-loader from the xdp-tools project[1], it exposes an option to set the 'pin-path' for a given program. However, programs loaded via tc don't appear to have that ability, all I have found is the use of LIBBPF_PIN_BY_NAME or the older PIN_OBJECT_NS/PIN_GLOBAL_NS, but those don't let the user specify the path. I've whipped up a quick patch to be able to pass along a 'pin_path' similar to the xdp-loader. I don't know if this is the *right* approach so I'm more than happy to be pointed in the right direction. Thanks Max [1] https://github.com/xdp-project/xdp-tools/tree/master/xdp-loader
Powered by blists - more mailing lists