On 15/09/2019 00:02, Tony Lindgren wrote:
Hi all,
Here are fixes and improvments for omap3-rom-rng that's been broken for
a while.
The first four patches get it working, and then the last two patches add
support for runtime PM.
I did not add Sebastian's acks from v1 set as many of the patches
Check if device supports assoclen to solve hung task timeout error when
extra tests are enabled. Return -EINVAL if assoclen is not supported.
Check authsize to return -EINVAL if authentication tag size is invalid.
Change blocksize to 1 to match with generic implementation.
Signed-off-by: Nagadheer
The return valude of add_comp_head() is int, but @head_size is size_t,
which is a unsigned type.
size_t head_size;
...
if (head_size < 0) // it will never work
return -ENOMEM
Modify the type of @head_size to int, then change the type to size_t
when invoke
On Fri, 13 Sep 2019 at 19:01, Jarkko Sakkinen
wrote:
>
> On Wed, Sep 11, 2019 at 04:51:50PM +0530, Sumit Garg wrote:
> > Switch to utilize common heap based tpm_buf code for TPM based
> > asymmetric keys rather than using stack based tpm_buf code.
> >
> > Reported-by: kbuild test robot
> > Signed
> -Original Message-
> From: Eric Biggers
> Sent: Sunday, September 15, 2019 10:21 PM
> To: Pascal Van Leeuwen
> Cc: Pascal van Leeuwen ; linux-crypto@vger.kernel.org;
> antoine.ten...@bootlin.com; herb...@gondor.apana.org.au; da...@davemloft.net
> Subject: Re: [PATCH 4/7] crypto: testmgr
Hi all,
Today's linux-next merge of the crypto tree got a conflict in:
arch/s390/crypto/aes_s390.c
between commit:
9e323d45ba94262 ("s390/crypto: xts-aes-s390 fix extra run-time crypto self
tests finding")
from the s390 tree and commit:
ce68acbcb6a5d5d ("crypto: s390/xts-aes - invoke f
Hi all,
Today's linux-next merge of the crypto tree got a conflict in:
arch/arm64/boot/dts/freescale/imx8mq.dtsi
between commit:
a99b26b14bea506 ("arm64: dts: imx8mq: Add MIPI D-PHY")
from the arm-soc tree and commit:
007b3cf0af8cb7d ("arm64: dts: imx8mq: Add CAAM node")
from the crypt
On Wed, Sep 11, 2019 at 07:34:31PM +, Pascal Van Leeuwen wrote:
> > -Original Message-
> > From: Eric Biggers
> > Sent: Wednesday, September 11, 2019 6:06 PM
> > To: Pascal van Leeuwen
> > Cc: linux-crypto@vger.kernel.org; antoine.ten...@bootlin.com;
> > herb...@gondor.apana.org.au;
On Sun, Sep 15, 2019 at 08:35:36PM +0200, Corentin Labbe wrote:
> When a TFM is unregistered, the sun4i-ss driver does not clean the key used,
> leaking it in memory.
> This patch adds this absent key cleaning.
>
> Fixes: 6298e948215f ("crypto: sunxi-ss - Add Allwinner Security System crypto
> ac
When a TFM is unregistered, the sun4i-ss driver does not clean the key used,
leaking it in memory.
This patch adds this absent key cleaning.
Fixes: 6298e948215f ("crypto: sunxi-ss - Add Allwinner Security System crypto
accelerator")
Cc: # 4.3+
Signed-off-by: Corentin Labbe
---
drivers/crypto/s
When dma_pool_zalloc() fail in sec_alloc_and_fill_hw_sgl(),
dma_pool_free() is invoked, but the parameters that sgl_current and
sgl_current->next_sgl is not match.
Using sec_free_hw_sgl() instead of the original free routine.
Fixes: 915e4e8413da ("crypto: hisilicon - SEC security accelerator driv
There are two problems in sec_free_hw_sgl():
First, when sgl_current->next is valid, @hw_sgl will be freed in the
first loop, but it free again after the loop.
Second, sgl_current and sgl_current->next_sgl is not match when
dma_pool_free() is invoked, the third parameter should be the dma
address
12 matches
Mail list logo
