NetBpfLoader: create /sys/fs/bpf/loader dir
(instead of in platform bpfloader) Better to do it earlier so we can use it for auto/permanently pinned/attached networking programs. Test: TreeHugger Signed-off-by: Maciej Żenczykowski <maze@google.com> Change-Id: I202e150e6d48e63ba643c1bd2247cefcdebc07a5
This commit is contained in:
parent
e816bb776a
commit
a9209da871
1 changed files with 7 additions and 0 deletions
|
|
@ -369,6 +369,13 @@ int main(int argc, char** argv, char * const envp[]) {
|
|||
if (createSysFsBpfSubDir(location.prefix)) return 1;
|
||||
}
|
||||
|
||||
// Note: there's no actual src dir for fs_bpf_loader .o's,
|
||||
// so it is not listed in 'locations[].prefix'.
|
||||
// This is because this is primarily meant for triggering genfscon rules,
|
||||
// and as such this will likely always be the case.
|
||||
// Thus we need to manually create the /sys/fs/bpf/loader subdirectory.
|
||||
if (createSysFsBpfSubDir("loader")) return 1;
|
||||
|
||||
// Load all ELF objects, create programs and maps, and pin them
|
||||
for (const auto& location : locations) {
|
||||
if (loadAllElfObjects(location) != 0) {
|
||||
|
|
|
|||
Loading…
Reference in a new issue