On Wed, Mar 16, 2022 at 01:10:41PM +1200, Herbert Xu wrote:
> On Wed, Dec 29, 2021 at 12:05:23PM +0100, Uwe Kleine-König wrote:
> > On Wed, Dec 29, 2021 at 01:05:54PM +1100, Herbert Xu wrote:
> > > On Wed, Dec 22, 2021 at 11:22:46AM +0100, Uwe Kleine-König wrote:
> > > >
> > > > I still experience a problem with the patch that got
> > > > adad556efcdd42a1d9e060cbe5f6161cccf1fa28 in v5.16-rc1. I saw there are
> > > > two commit fixing this one (
> > > > 
> > > > 	cad439fc040e crypto: api - Do not create test larvals if manager is disabled
> > > > 	e42dff467ee6 crypto: api - Export crypto_boot_test_finished
> > > > 
> > > > ) but I still encounter the following on 2f47a9a4dfa3:
> > > 
> > > Perhaps you missed the last fix?
> > > 
> > > commit beaaaa37c664e9afdf2913aee19185d8e3793b50
> > > Author: Herbert Xu <herbert@gondor.apana.org.au>
> > > Date:   Fri Nov 5 15:26:08 2021 +0800
> > > 
> > >     crypto: api - Fix boot-up crash when crypto manager is disabled
> > 
> > As 2f47a9a4dfa3 includes this commit, this is not the problem.
> 
> Using the config snippet in this email thread I was unable to
> reproduce the failure under qemu.  Can you still reproduce this
> with the latest upstream kernel? If yes please send me your complete
> config file.

Still happens on 5.17-rc8, config attached.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |