Tested kernel 5.3.0-43-generic from -proposed, on eoan with Secure
Boot/Lockdown enabled. Running 'sudo bpftool prog' works and lists BPF
programs loaded on the system, via the bpf() syscall. Same test on
5.3.0-42-generic would fail with -EPERM.
So the fix works well, and we can now use bpf()
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774815
Title:
Add bpftool to linux-tools-common
Not adding kernel logs but changing to 'Confirmed'.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863234
Title:
Public bug reported:
In disco and eoan, lockdown is automatically enforced when secure boot
is on [0]. Because lockdown was not in the mailine kernel at the time,
some disto-specific patches were added to the kernel, including one that
drastically restricts BPF usage by completely disabling the
Sent a patchset to package bpftool in linux-tools/linux-tools-common for
bionic, here is the related link:
https://lists.ubuntu.com/archives/kernel-team/2019-July/102462.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
5 matches
Mail list logo
