On Fri, Sep 20, 2019 at 06:35:56AM +0200, Steffen Klassert wrote: > > Fix this by making pcrypt forbid instantiation if pcrypt appears in the > underlying ->cra_driver_name or if an underlying algorithm needs a > fallback. This is somewhat of a hack, but it's a simple fix that should > be sufficient to prevent the deadlock. This still doesn't resolve the case where pcrypt is used in a non-transparent fashion, e.g., through a fallback. Note that even adding a NEED_FALLBACK flag won't fix this as you can construct an instance on top of a NEED_FALLBACK algorithm that itself does not need a fallback. Anyway I decided to change pcrypt to use a set of queues per instance rather than globally and it should resolve the problem. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
