diff options
| author | Horia Geantă <[email protected]> | 2018-03-28 15:39:18 +0300 |
|---|---|---|
| committer | Herbert Xu <[email protected]> | 2018-04-21 00:58:25 +0800 |
| commit | 115957bb3e59fcb226ce76b97af14533f239e0ac (patch) | |
| tree | 6748f1fafa791b6c84432a1d19b21734c61f5a31 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | a38acd236cac914aafffd80af79b9556fc2c3934 (diff) | |
crypto: caam - fix IV DMA mapping and updating
There are two IV-related issues:
(1) crypto API does not guarantee to provide an IV buffer that is DMAable,
thus it's incorrect to DMA map it
(2) for in-place decryption, since ciphertext is overwritten with
plaintext, updated req->info will contain the last block of plaintext
(instead of the last block of ciphertext)
While these two issues could be fixed separately, it's straightforward
to fix both in the same time - by allocating extra space in the
ablkcipher_edesc for the IV that will be fed to the crypto engine;
this allows for fixing (2) by saving req->src[last_block] in req->info
directly, i.e. without allocating another temporary buffer.
A side effect of the fix is that it's no longer possible to have the IV
and req->src contiguous. Code checking for this case is removed.
Cc: <[email protected]> # 4.13+
Fixes: 854b06f76879 ("crypto: caam - properly set IV after {en,de}crypt")
Link: http://lkml.kernel.org/r/[email protected]
Reported-by: Gilad Ben-Yossef <[email protected]>
Signed-off-by: Horia Geantă <[email protected]>
Signed-off-by: Herbert Xu <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions