crypto: doc - clarify hash callbacks state machine
Add a note that it is perfectly legal to "abandon" a request object: - call .init() and then (as many times) .update() - _not_ call any of .final(), .finup() or .export() at any point in future Link: https://lkml.kernel.org/r/20180222114741.GA27631@gondor.apana.org.au Signed-off-by: Horia Geantă <horia.geanta@nxp.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
parent
eb02c38f01
commit
0550f5a5f0
|
@ -236,6 +236,14 @@ when used from another part of the kernel.
|
|||
|
|
||||
'---------------> HASH2
|
||||
|
||||
Note that it is perfectly legal to "abandon" a request object:
|
||||
- call .init() and then (as many times) .update()
|
||||
- _not_ call any of .final(), .finup() or .export() at any point in future
|
||||
|
||||
In other words implementations should mind the resource allocation and clean-up.
|
||||
No resources related to request objects should remain allocated after a call
|
||||
to .init() or .update(), since there might be no chance to free them.
|
||||
|
||||
|
||||
Specifics Of Asynchronous HASH Transformation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
|
Loading…
Reference in a new issue