On Tue, Oct 26, 2021 at 09:33:19AM -0700, Guenter Roeck wrote: > Hi, > > On Fri, Sep 17, 2021 at 08:26:19AM +0800, Herbert Xu wrote: > > When complex algorithms that depend on other algorithms are built > > into the kernel, the order of registration must be done such that > > the underlying algorithms are ready before the ones on top are > > registered. As otherwise they would fail during the self-test > > which is required during registration. > > > > In the past we have used subsystem initialisation ordering to > > guarantee this. The number of such precedence levels are limited > > and they may cause ripple effects in other subsystems. > > > > This patch solves this problem by delaying all self-tests during > > boot-up for built-in algorithms. They will be tested either when > > something else in the kernel requests for them, or when we have > > finished registering all built-in algorithms, whichever comes > > earlier. > > > > Reported-by: Vladis Dronov <vdronov@xxxxxxxxxx> > > Signed-off-by: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > > > > I can not explain it, but this patch causes a crash with one of my boot > tests (riscv32 with riscv32 virt machine and e1000 network adapter): > > [ 9.948557] e1000 0000:00:01.0: enabling device (0000 -> 0003) Does this still occur with the latest patch I sent yesterday? Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
