Hi Scott, Thanks for sending this report in,
I've spoken with some people on the kernel team and it seems as though the biggest blockers preventing the config change are indeed absent in kernel versions after Noble. I've prepared an example kernel (questing) with IBT re-enabled and, assuming you have the hardware to do so, it would be nice if you could test it [1] to see if you can find any issues (especially if you have any external kernel modules like nvidia). I'll be doing the same on my end. If everything goes smoothly we can send a patch to the mailing list and get it included in the next kernel releases. [1] https://people.canonical.com/~cremfuelled/LP2122077/ -- 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/2122077 Title: X86_KERNEL_IBT was never re-enabled after being temporarily disabled Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Plucky: In Progress Status in linux source package in Questing: In Progress Bug description: X86_KERNEL_IBT was temporarily disabled on July 4, 2022 due to a localized bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980484. While it appears the bug was fixed, it appears X86_KERNEL_IBT was never re- enabled. Annotations in plucky show: $ cat annotations | grep KERNEL_IBT CONFIG_X86_KERNEL_IBT policy<{'amd64': 'n'}> CONFIG_X86_KERNEL_IBT note<'LP: #1980484'> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2122077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
