Re: [PATCH 1/2] crypto: marvell/cesa - fix memory leak

On Thu, 17 Mar 2016 10:21:34 +0100 Boris Brezillon wrote: > Crypto requests are not guaranteed to be finalized (->final() call), > and can be freed at any moment, without getting any notification from > the core. This can lead to memory leaks of the ->cache

[PATCH 1/2] crypto: marvell/cesa - fix memory leak

Crypto requests are not guaranteed to be finalized (->final() call), and can be freed at any moment, without getting any notification from the core. This can lead to memory leaks of the ->cache buffer. Make this buffer part of the request object, and allocate an extra buffer from the DMA cache