Hi,
On 11/02/2014 12:35 PM, Stephan Mueller wrote:
> + * type:
> + - blkcipher for symmetric block ciphers
blkcipher for synchronous block ciphers
> + - ablkcipher for asymmetric block ciphers
ablkcipher for asynchronous block ciphers
> + - cipher for sin
Hi Stephan,
Just one quick comment below...
regards,
Joy
On Sun, 2014-11-02 at 21:36 +0100, Stephan Mueller wrote:
> The API function calls exported by the kernel crypto API for RNGs to
> be used by consumers are documented.
>
> Signed-off-by: Stephan Mueller
> CC: Marek Vasut
> ---
> includ
Hi Stephan,
On Sun, 2014-11-02 at 21:36 +0100, Stephan Mueller wrote:
> The userspace interface of the kernel crypto API is documented with
> * a general explanation
> * a discussion of the memory in-place operation
> * the description of the message digest API
> * the description of the symme
Hi Stephan,
Great docs! I think they will be very useful! Thanks!
I only have 2 comments below.
regards,
Joy
On Sun, 2014-11-02 at 21:35 +0100, Stephan Mueller wrote:
> The design of the kernel crypto API as well as hints to program with
> the kernel crypto API are given.
>
> The documentation
On Wed, 5 Nov 2014 11:21:24 +0200
Cristian Stoica wrote:
> The error code returned by hardware is four bits wide with an expected
> zero MSB. A hardware error condition where the error code can get between
> 0x8 and 0xf will trigger an out of bound array access on the error
> message table.
> Thi
Hi Kim,
On 11/04/2014 06:57 PM, Kim Phillips wrote:
> On Tue, 4 Nov 2014 10:57:57 +0200
> Cristian Stoica wrote:
>> Do you want me to drop the patch and pretend there is nothing to see?
>
> no, fixing potential bugs preemptively is fine; I'd just like to
> know that's the case: it wasn't clear
The error code returned by hardware is four bits wide with an expected
zero MSB. A hardware error condition where the error code can get between
0x8 and 0xf will trigger an out of bound array access on the error
message table.
This patch fixes the invalid array access following such an error and
re
