Seems I need to be more careful what I write here, as it seems one of my sneaky remarks lead to a #Linux #Kernel patch.
powerpc/boot: Remove bogus reference to #lilo – https://lore.kernel.org/all/20241009053806.135807-1-mpe@ellerman.id.au/
From @mpe – and according to the Link tag triggered by https://fosstodon.org/@kernellogger/113032940928131612 (see Screenshot)
@kernellogger @mpe or, maybe you should be less careful in order to generate more kernel patches
@Aissen @kernellogger @mpe Thorsten, we're all hanging on your lips, ready to make patches like crazy!
> Thorsten, we're all hanging on your lips, ready to make patches like crazy!
Be careful what you say, otherwise I might follow your advice.
I was tempted a few hours ago -- but quickly decided submitting a rough patch myself is the way better approach.
See https://lore.kernel.org/all/42aa307d7ffae1851b4a8787f5c276dd0b3beece.1728543368.git.linux@leemhuis.info/ or https://fosstodon.org/@kernellogger/113281883813298472 for details.
@kernellogger @ljs @mpe @ptesarik @Aissen Soon we get to report regressions against the regression tracker yehaaw
@kernellogger @ptesarik @Aissen @mpe You can also add "default MODULE_SIG_SHA256" or whatever to the "choice" section above it so you don't have an implicit dependency on the ordering.
@vegard fwiw, it's not that easy afaics, as the real choice that matters is in another place that has some trickery: https://lore.kernel.org/all/c94590a5-4121-497b-8529-cbab2b01fe51@leemhuis.info/
@kernellogger @vegard MODULE_SIG_HASH is not a choice, it's a string that is set based on which of the MODULE_SIG_SHAxxx options was selected above. You shouldn't need to touch that section.
Adding `default MODULE_SIG_SHA512` to the choice (~line 234) should do it.
I don't think that's a problem.
Only one of the MODULE_SIG_SHAxxx options can ever be enabled at a time - because they're inside a `choice`.
More than one *algorithm* can still be enabled, but those are the CRYPTO_SHAxxx symbols, not the MODULE_SIG_SHAxxx ones.