-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bump libbpf to map creation upstream fix #305
Labels
bug
Something isn't working
Comments
geyslan
added a commit
to geyslan/libbpfgo
that referenced
this issue
Mar 23, 2023
This is a minor bump to include the following libbpf fix: libbpf: Fix map creation flags sanitization As BPF_F_MMAPABLE flag is now conditionnaly set (by map_is_mmapable), it should not be toggled but disabled if not supported by kernel. Fixes: aquasecurity#305
Merged
We can't checkout libbpf/libbpf@ce8d078, since there were other changes related to map what bumped it to 1.2 while libbpf remained 1.1. See build error: So the actual bump needs to be to 1.2 - libbpf/libbpf@b2e29a1. |
geyslan
added a commit
to geyslan/libbpfgo
that referenced
this issue
Mar 23, 2023
This is a minor bump to include the following libbpf fix (and all the related changes in libbpf submodule): libbpf: Fix map creation flags sanitization As BPF_F_MMAPABLE flag is now conditionnaly set (by map_is_mmapable), it should not be toggled but disabled if not supported by kernel. Fixes: aquasecurity#305
rafaeldtinoco
pushed a commit
that referenced
this issue
Mar 24, 2023
This is a minor bump to include the following libbpf fix (and all the related changes in libbpf submodule): libbpf: Fix map creation flags sanitization As BPF_F_MMAPABLE flag is now conditionnaly set (by map_is_mmapable), it should not be toggled but disabled if not supported by kernel. Fixes: #305
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
libbpf v1.1.0 is failing with kernels without
BPF_F_MMAPABLE
support.libbpf must be bumped to the upstream:
libbpf/libbpf@ce8d078-> libbpf/libbpf@b2e29a1 (see comment below)Context:
The text was updated successfully, but these errors were encountered: