On Wed, Jul 29, 2009 at 03:58:10PM -0700, Shasi Pulijala wrote: > > I am assuming you are talking about the final hash result being stored in the ctx of the tfm and not the intermediate hash state. No I mean the intermediate hash state. All crypto hash implementations must support crypto_ahash_init(req1) crypto_ahash_init(req2) crypto_ahash_update(req1) crypto_ahash_update(req2) crypto_ahash_final(req1) crypto_ahash_final(req2) Of course there may be an unlimited number of requests and these may be invoked from different CPUs. Therefore you must store the intermediate hash result in the request itself. If your particular device does not support the export of the intermediate state, then you must fall back to using a software hash for everything up until the last finup/final request. See drivers/crypto/padlock-sha.c for an example. It's shash but the same principle applies to ahash. Only the old hash/digest interface is limited to one request per tfm at any time. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
