On Thu, Mar 13, 2014 at 02:20:29AM +0100, Marek Vasut wrote: > > OK, understood. But shall we not preserve the request intact in case a crypto- > api function called crypto_ahash_final() with request which has .priv already > set? Then we would have really funny corruption of the request going on and I'm > not sure that'd be nice. The priv field is only ever used by ahash.c so how can this happen? The crypto API refers to code in the API itself, excluding drivers and users. Cheers, -- Email: Herbert Xu <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
