Searched hist:"3 c44d31cb34ce4eb8311a2e73634d57702948230" (Results 1 – 4 of 4) sorted by relevance
| /linux/include/crypto/internal/ |
| H A D | simd.h | diff 3c44d31cb34ce4eb8311a2e73634d57702948230 Sat Aug 17 08:58:35 CEST 2024 Herbert Xu <herbert@gondor.apana.org.au> crypto: simd - Do not call crypto_alloc_tfm during registration
Algorithm registration is usually carried out during module init,
where as little work as possible should be carried out. The SIMD
code violated this rule by allocating a tfm, this then triggers a
full test of the algorithm which may dead-lock in certain cases.
SIMD is only allocating the tfm to get at the alg object, which is
in fact already available as it is what we are registering. Use
that directly and remove the crypto_alloc_tfm call.
Also remove some obsolete and unused SIMD API.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
|
| /linux/crypto/ |
| H A D | simd.c | diff 3c44d31cb34ce4eb8311a2e73634d57702948230 Sat Aug 17 08:58:35 CEST 2024 Herbert Xu <herbert@gondor.apana.org.au> crypto: simd - Do not call crypto_alloc_tfm during registration
Algorithm registration is usually carried out during module init,
where as little work as possible should be carried out. The SIMD
code violated this rule by allocating a tfm, this then triggers a
full test of the algorithm which may dead-lock in certain cases.
SIMD is only allocating the tfm to get at the alg object, which is
in fact already available as it is what we are registering. Use
that directly and remove the crypto_alloc_tfm call.
Also remove some obsolete and unused SIMD API.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
|
| /linux/arch/arm/crypto/ |
| H A D | aes-neonbs-glue.c | diff 3c44d31cb34ce4eb8311a2e73634d57702948230 Sat Aug 17 08:58:35 CEST 2024 Herbert Xu <herbert@gondor.apana.org.au> crypto: simd - Do not call crypto_alloc_tfm during registration
Algorithm registration is usually carried out during module init,
where as little work as possible should be carried out. The SIMD
code violated this rule by allocating a tfm, this then triggers a
full test of the algorithm which may dead-lock in certain cases.
SIMD is only allocating the tfm to get at the alg object, which is
in fact already available as it is what we are registering. Use
that directly and remove the crypto_alloc_tfm call.
Also remove some obsolete and unused SIMD API.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
|
| H A D | aes-ce-glue.c | diff 3c44d31cb34ce4eb8311a2e73634d57702948230 Sat Aug 17 08:58:35 CEST 2024 Herbert Xu <herbert@gondor.apana.org.au> crypto: simd - Do not call crypto_alloc_tfm during registration
Algorithm registration is usually carried out during module init,
where as little work as possible should be carried out. The SIMD
code violated this rule by allocating a tfm, this then triggers a
full test of the algorithm which may dead-lock in certain cases.
SIMD is only allocating the tfm to get at the alg object, which is
in fact already available as it is what we are registering. Use
that directly and remove the crypto_alloc_tfm call.
Also remove some obsolete and unused SIMD API.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
|