You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The strange behavior I am seeing is that the result of this command is that the /sys/fs/cgroup directory is deleted when it existed prior to calling this command:
$ sudo ls -l /sys/fs/cgroup
ls: cannot access /sys/fs/cgroup: No such file or directory
This causes issues for initialization of systemd services which are using cgroup to limit memory consumption which I am trying to initialize after loading the BPF program. Is this behavior expected and is there some workaround I can apply?
The text was updated successfully, but these errors were encountered:
ndejaco2
changed the title
BPFTool command Deletes /sys/fs/cgroup virtual file system directory.
BPFTool command Deletes /sys/fs/cgroup virtual file system directory
Dec 7, 2023
ndejaco2
changed the title
BPFTool command Deletes /sys/fs/cgroup virtual file system directory
BPFTool Prog Loadall command Deletes /sys/fs/cgroup virtual file system directory
Dec 7, 2023
This looks like a consequence of #100, with bpftool mistakenly re-mounting the bpffs on top of the parent directory of your path (/sys/fs/) and masking the previous contents of the directory.
This needs to be fixed, but in the meantime, you can probably work around it by passing another path to pin your programs? bpftool prog loadall ... pinmaps /sys/fs/bpf/myProgram?
I am using the following BPFTool version:
bpftool v7.3.0
using libbpf v1.3
Linux version: 4.14.328-248.540.amzn2.aarch64
I am running a command to load my BPF program like so:
The strange behavior I am seeing is that the result of this command is that the /sys/fs/cgroup directory is deleted when it existed prior to calling this command:
This causes issues for initialization of systemd services which are using cgroup to limit memory consumption which I am trying to initialize after loading the BPF program. Is this behavior expected and is there some workaround I can apply?
The text was updated successfully, but these errors were encountered: