On Wed, Jun 10, 2015 at 10:27:48PM +0900, Sergey Senozhatsky wrote:
> Be more verbose and also report ->backend_cra_name when
> crypto_alloc_shash() or crypto_alloc_cipher() fail in
> drbg_init_hash_kernel() or drbg_init_sym_kernel()
> correspondingly.
>
> Example
> DRBG: could not allocate diges
On (06/10/15 17:09), Stephan Mueller wrote:
> Hi Sergey,
>
> >Be more verbose and also report ->backend_cra_name when
> >crypto_alloc_shash() or crypto_alloc_cipher() fail in
> >drbg_init_hash_kernel() or drbg_init_sym_kernel()
> >correspondingly.
> >
> >Example
> > DRBG: could not allocate digest
Am Wednesday 10 June 2015, 22:27:48 schrieb Sergey Senozhatsky:
Hi Sergey,
>Be more verbose and also report ->backend_cra_name when
>crypto_alloc_shash() or crypto_alloc_cipher() fail in
>drbg_init_hash_kernel() or drbg_init_sym_kernel()
>correspondingly.
>
>Example
> DRBG: could not allocate dig
Be more verbose and also report ->backend_cra_name when
crypto_alloc_shash() or crypto_alloc_cipher() fail in
drbg_init_hash_kernel() or drbg_init_sym_kernel()
correspondingly.
Example
DRBG: could not allocate digest TFM handle: hmac(sha256)
Signed-off-by: Sergey Senozhatsky
---
crypto/drbg.c