[PATCH] crypto: akcipher: fix typos in include/crypto/akcipher.h

Fix numerous spelling error in include/crypto/akcipher.h Signed-off-by: LABBE Corentin --- include/crypto/akcipher.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h index

[PATCH v2 1/4] crypto: hash: add zero length message hash for shax and md5

Some crypto drivers cannot process empty data message and return a precalculated hash for md5/sha1/sha224/sha256. This patch add thoses precalculated hash in include/crypto. Signed-off-by: LABBE Corentin --- crypto/md5.c| 6 ++ crypto/sha1_generic.c

[PATCH v2 4/4] crypto: ux500: Use precalculated hash from headers

Precalculated hash for empty message are now present in hash headers. This patch just use them. Signed-off-by: LABBE Corentin --- drivers/crypto/ux500/hash/hash_core.c | 20 ++-- 1 file changed, 2 insertions(+), 18 deletions(-) diff --git

[PATCH v2 3/4] crypto: ccp: Use precalculated hash from headers

Precalculated hash for empty message are now present in hash headers. This patch just use them. Signed-off-by: LABBE Corentin Tested-by: Tom Lendacky Acked-by: Tom Lendacky --- drivers/crypto/ccp/ccp-ops.c | 39

[PATCH v2 2/4] crypto: niagara: Use precalculated hash from headers

Precalculated hash for empty message are now present in hash headers. This patch just use them. Signed-off-by: LABBE Corentin --- drivers/crypto/n2_core.c | 33 ++--- 1 file changed, 6 insertions(+), 27 deletions(-) diff --git

[PATCH v2 0/4] crypto: add precalculated hash for zero message length

Hello Some crypto drivers cannot process empty data message and so rely on precalculated hash. This patch series add precalculated hash in headers and make the drivers use them. Using those precalculated hash make some additionnal constify patch necessary. Changes since v1 - Moved arrays from

Re: ipsec impact on performance

On (12/08/15 12:32), Steffen Klassert wrote: > > Would be nice if you could share the results. Comments are Sure, not a problem. Give me some time though, I'm also looking into the skb_cow_data and other memory-management issues that were flagged on this thread. I'll have all this info by

WARNING in crypto_wait_for_test

Hello, The following program triggers a WARNING in crypto_wait_for_test: // autogenerated by syzkaller (http://github.com/google/syzkaller) #include #include #include int main() { long r0 = syscall(SYS_mmap, 0x2000ul, 0x1000ul, 0x3ul, 0x32ul, 0xul, 0x0ul);

Re: ipsec impact on performance

On Mon, Dec 07, 2015 at 06:27:48AM -0500, Sowmini Varadhan wrote: > On (12/07/15 09:40), Steffen Klassert wrote: > > > > I've pushed it to > > > > https://git.kernel.org/cgit/linux/kernel/git/klassert/linux-stk.git/log/?h=net-next-ipsec-offload > > > > It is just example code, nothing that I

[PATCH 1/2] crypto: sahara: fix 64-bit dma_addr_t compilation

The sahara hardware uses DMA descriptors with 32-bit addresses, but dma_addr_t is variable size depending on whether we want to support any devices that use 64-bit DMA addresses in hardware. This means that the definition of the DMA descriptor structure is wrong, and we helpfully get a compiler

[PATCH 2/2] crypto: sahara: fix debug output for 64-bit dma_addr_t

The sahara_dump_descriptors and sahara_dump_links functions attempt to print a dma_addr_t value with a 0x%08x format string, which produces a warning when dma_addr_t is 64-bit wide: drivers/crypto/sahara.c:419:120: warning: format '%x' expects argument of type 'unsigned int', but argument 5 has

Re: [PATCH v4 5/5] crypto: AES CBC multi-buffer glue code

On Wed, Dec 02, 2015 at 12:02:45PM -0800, Tim Chen wrote: > > +/* > + * CRYPTO_ALG_ASYNC flag is passed to indicate we have an ablk > + * scatter-gather walk. > + */ > + > +static struct crypto_alg aes_cbc_mb_alg = { > + .cra_name = "__cbc-aes-aesni-mb", > + .cra_driver_name