Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: 2018-02-22 11:47:58
Also in:
linuxppc-dev, lkml
Possibly related (same subject, not in this thread)
- 2018-02-17 · Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests · Christophe LEROY <hidden>
- 2018-02-07 · Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests · Horia Geantă <horia.geanta@nxp.com>
- 2017-10-06 · [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests · Christophe Leroy <hidden>
On Tue, Feb 20, 2018 at 11:32:25AM +0000, Horia Geantă wrote:
If final/finup is optional, how is the final hash supposed to be retrieved?
Sometimes the computation ends with a partial hash, that's what export is for. Also it is completely legal to abandon the hash state entirely.
According to documentation, these are the accepted flows (with the option to
export/import a partial hash b/w update and final/finup):
.init() -> .update() -> .final()
^ | |
'----' '---> HASH
.init() -> .update() -> .finup()
^ | |
'----' '---> HASH
.digest()
|
'---------------> HASHThe documentation is simply incomplete in this regard. Cheers, -- Email: Herbert Xu [off-list ref] Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt