lkml.org 
[lkml]   [2015]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH v6 1/5] random: Blocking API for accessing nonblocking_pool
Date
Am Montag, 18. Mai 2015, 11:02:34 schrieb Theodore Ts'o:

Hi Theodore, Herbert,
>
> The simplest thing to do is to put a refcount on inside the DRBG
> handle structure. The caller instantiates the DRBG handle, and
> invokes the the DRBG. The DRBG, since it is kicking off an
> asynchronous operation, increments the refcount.

That is a good idea. After experimenting with the refcount, I see that kernel
crypto API release function of crypto_destroy_tfm unconditionally destroys the
crypto handle by freeing it.

So, if a caller releases the DRBG handle, the DRBG code cannot prevent the
destruction of its context with a refcount.

Herbert, do you have any ideas?

--
Ciao
Stephan


\
 
 \ /
  Last update: 2015-05-19 09:41    [W:0.046 / U:0.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site