On Mon, Aug 10, 2026 at 11:31:10AM +0100, Will Deacon wrote: > On Fri, Aug 07, 2026 at 02:46:11PM -0700, Josh Poimboeuf wrote:
> > The following BTI exception was seen when loading a livepatch module: > > Internal error: Oops - BTI: 0000000036000001 [#1] SMP > > pstate: 634004c9 (nZCv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=jc) > > pc : kill_orphaned_pgrp+0x0/0x150 > > lr : do_exit+0x498/0xaf0 [livepatch_combined] > > This was found by testing with klp-build and Clang 21, but the issue is > > not specific to klp-build. It's inherent to any livepatch module use of > > klp relocations. > > Previous tests with Clang 20 did not show this problem, as older Clang > > unconditionally emits "bti c" for every C function. > Is there an option to restore that behaviour if CONFIG_LIVEPATCH=y? > Otherwise, I think I'd be more inclined to add yet-another dependency > to CONFIG_ARM64_BTI_KERNEL so it's disabled if LIVEPATCH is selected. This won't even be livepatch specific I think - I expect the same issue can be triggered for module loading by using annotations to place functions from the same translation unit in different sections if the sections get placed far enough apart. That was what was impacting GCC.
signature.asc
Description: PGP signature
