LF-1782-2 Revert "dm crypt: don't use drivers that have CRYPTO_ALG_ALLOCATES_MEMORY"

commit f5b981c5c5a5a7cbd0a755e3211277dbe7c8bb49 from
https://source.codeaurora.org/external/imx/linux-imx

This reverts commit cd746938.

This is a workaround for allowing dm-crypt crypto operations to be
offloaded to caam crypto accelerator.
It's needed because crypto algorithms registered by caam are marked with
CRYPTO_ALG_ALLOCATES_MEMORY flag.

Background:
Red Hat reported possible allocation issues in dm-crypt, dm-integrity:
Link: https://lore.kernel.org/linux-crypto/alpine.LRH.2.02.2006091259250.30590@file01.intranet.prod.int.rdu2.redhat.com


The solution found was a mechanism to let dm-crypt, dm-integrity avoid
using crypto algorithms that allocate memory "at runtime" - by specifying
the CRYPTO_ALG_ALLOCATES_MEMORY flag introduced in
commit fbb6cda4 ("crypto: algapi - introduce the flag CRYPTO_ALG_ALLOCATES_MEMORY")

Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
Reviewed-by: Manish Tomar <manish.tomar@nxp.com>