On 08.05.2025 18:03, Andrew Cooper wrote: > The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already stale > by the time speculative vulnerabilities hit the headlines in 2018. It is > specifically an out-of-line-ing mechansim, and repoline is one of several > safety sequences used. > > Some of this boilerplate has been copied into all other options, and isn't > interesting for the target audience given that they're all in a "Speculative > Hardning" menu. > > Reword it to be more concise. > > No functional change. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> > --- > CC: Anthony PERARD <anthony.per...@vates.tech> > CC: Michal Orzel <michal.or...@amd.com> > CC: Jan Beulich <jbeul...@suse.com> > CC: Julien Grall <jul...@xen.org> > CC: Roger Pau Monné <roger....@citrix.com> > CC: Stefano Stabellini <sstabell...@kernel.org> > > CONFIG_SPECULATIVE_HARDEN_BRANCH really ought to be named > CONFIG_SPECULATIVE_HARDEN_CONDITIONAL, but this would be a (minor) functional > change.
Hmm, so you're suggesting all the straight-line speculation changes then ought to be conditional upon a separate, new Kconfig control? So far I've keyed them all to this one. Jan
