On Tue, Jan 14, 2014 at 06:31:01PM +0100, Marek Vasut wrote: > Move the AES operation type and mode from async crypto context to > crypto request context. This allows for recycling of the async crypto > context for different kinds of operations. > > I found this problem when I used dm-crypt, which uses the same async > crypto context (actx) for both encryption and decryption requests. > Since the requests are enqueued into the processing queue, immediatelly > storing the type of operation into async crypto context (actx) caused > corruption of this information when encryption and decryption operations > followed imediatelly one after the other. When the first operation was > dequeued, the second operation was already enqueued and overwritten the > type of operation in actx, thus causing incorrect result of the first > operation. > > Fix this problem by storing the type of operation into the crypto request > context. > > Signed-off-by: Marek Vasut <ma...@denx.de> > Cc: David S. Miller <da...@davemloft.net> > Cc: Fabio Estevam <fabio.este...@freescale.com> > Cc: Herbert Xu <herb...@gondor.apana.org.au> > Cc: Shawn Guo <shawn....@linaro.org> > Cc: Tom Lendacky <thomas.lenda...@amd.com>
Patch applied. -- Email: Herbert Xu <herb...@gondor.apana.org.au> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
