linux-kernel - Re: [V3 PATCH 0/2] fix some CAAM warnings.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 9 Mar 2015 21:07:31 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	yanjiang.jin@...driver.com
Cc:	horia.geanta@...escale.com, davem@...emloft.net,
	kim.phillips@...escale.com, ruchika.gupta@...escale.com,
	cristian.stoica@...escale.com, NiteshNarayanLal@...escale.com,
	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
	jinyanjiang@...il.com
Subject: Re: [V3 PATCH 0/2]  fix some CAAM warnings.

On Fri, Mar 06, 2015 at 10:34:40AM +0800, yanjiang.jin@...driver.com wrote:
> From: Yanjiang Jin <yanjiang.jin@...driver.com>
> 
> Hi,
> 
> This patch series fix some CAAM compile and runtime warnings.
> 
> I have tested this on fsl-p5020ds board using upstream 4.0.0-rc2 with the below configs:
> 
> CONFIG_DMA_API_DEBUG=y
> # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
> 
> Change log:
> v3:
> 
> 0001-crypto-caamhash-fix-uninitialized-edesc-sec4_sg_byte.patch is same as before.
> 
> For 0002-crypto-caam_rng-fix-rng_unmap_ctx-s-DMA_UNMAP-size-p.patch
> 1. Fix an alignment issue;
> 2. update DESC_RNG_LEN to (4 * CAAM_CMD_SZ).
> 
> Abandon the v2 patch 0001-crypto-caam-fix-some-compile-warnings.patch.

All applied.  Thanks
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/