On Mon, Oct 07, 2024 at 12:32:22PM +0800, Herbert Xu wrote: > > PS it looks like there is an actual report of things breaking with > async testing in mv_cesa so I might revert/disable the async testing > after all. It looks like it wasn't a bug in the async self-test. Instead this appears to be a real bug that was discovered by the async testing (because we now run all the tests at the same time, thus testing the whether the driver deals with parallel requests or not). This is a bit accidental, because the driver in question registered multiple hash algorithms. Had it only registered one, then nothing would have changed. Is this something that we could improve in testmgr? Perhaps we can add a bit of parallelism ourselves to cover the case where a driver only registers one hash algorithm. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
