Hi Florian, (+ Eric in Cc) On 12/08/2025 11:22, Florian Westphal wrote: > Paolo Abeni <pabeni@xxxxxxxxxx> wrote: >>> I don't see relevant patches landing in the relevant builds, I suspect >>> the relevant kernel config knob (CONFIG_CRYPTO_SHA1 ?) was always >>> missing in the ST config, pulled in by NIPA due to some CI setup tweak >>> possibly changed recently (Jakub could possibly have a better idea/view >>> about the latter). Could you please have a look? > > Can't reproduce this here. > > Latest net tree: I don't know if it can help, but did you try to reproduce it on top of the branch used by the CI? https://github.com/linux-netdev/testing/tree/net-next-2025-08-12--06-00 This branch is on top of net-next, where 'net' has been merged, all pending patches listed on Patchwork have been applied, plus a few additional patches are there to either fix some temp issues or improve the CI somehow. Maybe one of these patches caused the removal of CONFIG_CRYPTO_SHA1. I guess that's the case, because when looking at the diff [1] when the issue got introduced, I see some patches [2] from Eric Biggers modifying some sctp's Kconfig file. They probably cause the issue, but the fix should be to add CONFIG_CRYPTO_SHA1 in the ST config as mentioned by Paolo. [1] https://netdev.bots.linux.dev/static/nipa/branch_deltas/net-next-2025-08-12--03-00.html [2] https://patchwork.kernel.org/project/netdevbpf/list/?series=990201 Cheers, Matt -- Sponsored by the NGI0 Core fund.
