Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: perf-tools-unstable (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862708
Re: PermissionError: [Errno 1] Operation not permitted:
'/sys/kernel/debug/tracing/../kprobes/blacklist'
This can be fixed by a patch to the bpfcc libs found at:
https://github.com/iovisor/bcc/commit/5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a?branch=5558e36bd97ace7bc3efe3a70d0c9d4fc0d34e2a=unified
Just to be clear, not *all* tracing tools work, but this is much better:
sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ sudo zfsslower-bpfcc
Traceback (most recent call last):
Marking 'Fix Released' after the lockdown changes.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862708
Title:
tracing
I'm sorry for the slow response Francis, I've been running custom kernels for:
https://bugs.launchpad.net/bugs/1861359
for a while. Thanks for the reminder.
sarnold@millbarge:~$ dmesg | grep -i lockdown
[0.00] Kernel is locked down from EFI Secure Boot mode; see man
kernel_lockdown.7
[
@seth-arnold,
Lockdown has been relaxed in the latest kernel, 5.4.0-20.24: "SAUCE:
(lockdown) Reduce lockdown level to INTEGRITY for secure boot".
Can you please retest with the kernel from focal-proposed or this PPA:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed
--
You
I couldn't find a way to disable the lockdown functionality short of
disabling secure boot in my UEFI system setup.
If we choose to keep lockdown enabled by default then we will need to
document a way it can be disabled so users can run applications like
https://cilium.io/ or the bcc iovisor
This is an upstream behavior under lockdown "confedentiality" mode:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ccbd54ff54e8b1880456b81c4aea352ebe208843
Possibly there's an argument that the information disclosure isn't
severe enough that it needs to be
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862708
Title:
tracing doesn't work on focal
To manage notifications about this
apport information
** Tags added: apport-collected
** Description changed:
Hello, while investigating bug 1861359 I tried to use kprobe-perf to
troubleshoot and found that tracing doesn't work on focal:
# kprobe-perf -s 'p:shrink_node'
ERROR: func shrink_node not in
10 matches
Mail list logo
