Re: [PATCH] crypto: sha1-powerpc: little-endian support

2016-10-03 Thread Michael Ellerman
Marcelo Cerri writes: > [ Unknown signature status ] > On Wed, Sep 28, 2016 at 09:20:15PM +0800, Herbert Xu wrote: >> On Wed, Sep 28, 2016 at 10:15:51AM -0300, Marcelo Cerri wrote: >> > Hi Herbert, >> > >> > Any thoughts on this one? >> >> Can this patch wait until the next merge window? On the

RE: sha1_mb broken

2016-10-03 Thread Dey, Megha
-Original Message- From: Stephan Mueller [mailto:smuel...@chronox.de] Sent: Wednesday, September 28, 2016 10:31 PM To: Dey, Megha Cc: linux-crypto@vger.kernel.org; tim.c.c...@linux.intel.com Subject: Re: sha1_mb broken Am Mittwoch, 28. September 2016, 22:52:46 CEST schrieb Dey, Megha:

Re: Moving from blkcipher to skcipher

2016-10-03 Thread Stephan Mueller
Am Montag, 3. Oktober 2016, 10:58:03 CEST schrieb Alex Cope: Hi Alex, > I was unclear in my initial message. I'm implementing a block cipher > mode of operation. I'm hoping there is a another block cipher mode of > operation that already uses skcipher, so I can use it as a reference > and avoid r

Re: Moving from blkcipher to skcipher

2016-10-03 Thread Alex Cope
I was unclear in my initial message. I'm implementing a block cipher mode of operation. I'm hoping there is a another block cipher mode of operation that already uses skcipher, so I can use it as a reference and avoid re-inventing the wheel. In particular, it would be helpful if there is some imple

Re: Moving from blkcipher to skcipher

2016-10-03 Thread Stephan Mueller
Am Montag, 3. Oktober 2016, 10:06:23 CEST schrieb Alex Cope: Hi Alex, > I'm currently working on implementing HEH encryption, and am in the > process of switching from the blkcipher interface to the skcipher > interface. All the examples I have found that use skcipher are > wrapping another mode

Moving from blkcipher to skcipher

2016-10-03 Thread Alex Cope
I'm currently working on implementing HEH encryption, and am in the process of switching from the blkcipher interface to the skcipher interface. All the examples I have found that use skcipher are wrapping another mode of operation I.E. cts in cts(cbc(aes)) rather than being directly above the blo

Re: [PATCH v2 0/2] Improve DMA chaining for ahash requests

2016-10-03 Thread Romain Perier
Hello, Le 03/10/2016 17:17, Romain Perier a écrit : This series contain performance improvement regarding ahash requests. So far, ahash requests were systematically not chained at the DMA level. However, in some case, like this is the case by using IPSec, some ahash requests can be processed dir

[PATCH v2 1/2] crypto: marvell - Use an unique pool to copy results of requests

2016-10-03 Thread Romain Perier
So far, we used a dedicated dma pool to copy the result of outer IV for cipher requests. Instead of using a dma pool per outer data, we prefer use the op dma pool that contains all part of the request from the SRAM. Then, the outer data that is likely to be used by the 'complete' operation, is copi

[PATCH v2 2/2] crypto: marvell - Don't break chain for computable last ahash requests

2016-10-03 Thread Romain Perier
Currently, the driver breaks chain for all kind of hash requests in order to don't override intermediate states of partial ahash updates. However, some final ahash requests can be directly processed by the engine, and so without intermediate state. This is typically the case for most for the HMAC r

[PATCH v2 0/2] Improve DMA chaining for ahash requests

2016-10-03 Thread Romain Perier
This series contain performance improvement regarding ahash requests. So far, ahash requests were systematically not chained at the DMA level. However, in some case, like this is the case by using IPSec, some ahash requests can be processed directly by the engine, and don't have intermediaire parti

Re: [PATCH 0/3] Fix crypto/vmx/p8_ghash memory corruption

2016-10-03 Thread Marcelo Cerri
Hi Herbert, Sorry for bothering you. I noticed you included two of the patches in the crypto-2.6 repository and the remaining one in cryptodev-2.6. Is that right? I thought all 3 patches would be included in the cruptodev repository. -- Regards, Marcelo On Wed, Sep 28, 2016 at 01:42:08PM -0300,

[PATCH v2 1/1] crypto: atmel-aes: add support to the XTS mode

2016-10-03 Thread Cyrille Pitchen
This patch adds the xts(aes) algorithm, which is supported from hardware version 0x500 and above (sama5d2x). Signed-off-by: Cyrille Pitchen --- ChangeLog: v1 -> v2: - fix typo in comment inside atmel_aes_xts_process_data(): s/reverted/reversed/ - use xts_check_key() from atmel_aes_xts_setkey()

Re: [PATCH 0/3] Fix crypto/vmx/p8_ghash memory corruption

2016-10-03 Thread Marcelo Cerri
Thank you. -- Regards, Marcelo On Sun, Oct 02, 2016 at 10:40:47PM +0800, Herbert Xu wrote: > On Thu, Sep 29, 2016 at 06:59:08AM +1000, Anton Blanchard wrote: > > Hi Marcelo > > > > > This series fixes the memory corruption found by Jan Stancek in > > > 4.8-rc7. The problem however also affects

Re: [BUG] crypto: atmel-aes - erro when compiling with VERBOSE_DEBUG enable

2016-10-03 Thread Cyrille Pitchen
Hi all, Le 02/10/2016 à 16:38, Herbert Xu a écrit : > On Tue, Sep 27, 2016 at 06:45:18PM +0200, Cyrille Pitchen wrote: >> Hi Levent, >> >> there is a typo in the subject line: erroR. >> Also it would be better to start the summary phrase of the subject line with >> a >> verb: >> >> crypto: atmel-