After discussing the the kernel team this seems to be the correct behavior and output. This is obviously okay: "Kernel is locked down from command line; see man kernel_lockdown.7" but the further msgs like "Lockdown: swapper/0: use of tracefs..." seem to be right.
Just waiting for another quick test based on the very latest kernel 5.4 from the archives (the one above was from the PPA) and if the output is similar, we can consider this as done. Changing to Fix Committed. ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-power-systems Status: Triaged => Fix Committed -- 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/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Michael Ranweiler <mranw...@us.ibm.com> - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp