Re: [Ocf-linux-users] OCF_CRYPTOSOFT depends on CRYPTO_MANAGER

[David M. <dav...@mc...>]

Jivin Hauke Mehrtens lays it down ...
> Hi,
> 
> I am getting the following error while loading cryptosoft on an bcm47xx
> mips device. The attached patch fixes the problem.
> 
> cryptosoft: Unknown symbol crypto_alloc_ahash (err 0)
> cryptosoft: Unknown symbol crypto_ahash_setkey (err 0)
> cryptosoft: Unknown symbol crypto_alloc_ablkcipher (err 0)
> cryptosoft: Unknown symbol crypto_ahash_digest (err 0)

Ok,  I look at adding a fix into the tree.

CRYPTO_MANAGER is a little overkill though,  I think you just need to have
CRYPTO_HASH enabled.  Could you check with just that ?

Thanks,
Davidm

> --- a/crypto/ocf/Kconfig
> +++ b/crypto/ocf/Kconfig
> @@ -26,6 +26,7 @@ config OCF_CRYPTODEV
>  
>  config OCF_CRYPTOSOFT
>  	tristate "cryptosoft (software crypto engine)"
> +	select CRYPTO_MANAGER
>  	depends on OCF_OCF
>  	help
>  	  A software driver for the OCF framework that uses

> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/

> _______________________________________________
> Ocf-linux-users mailing list
> Ocf...@li...
> https://lists.sourceforge.net/lists/listinfo/ocf-linux-users


-- 
David McCullough,      dav...@mc...,  Ph:+61 734352815
McAfee - SnapGear      http://www.mcafee.com         http://www.uCdot.org