summaryrefslogtreecommitdiff
path: root/include/keys
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2022-03-26 10:11:59 +0300
committerHerbert Xu <herbert@gondor.apana.org.au>2022-04-08 11:25:19 +0300
commitf17f9e9069f20f4400ae0bb3ee830d34104ff8f7 (patch)
tree8da45b390dccac99e638d680c35b25e1c182c1a3 /include/keys
parentf16a005cde3b1f31cad5ecba0cc810652c3874ec (diff)
downloadlinux-f17f9e9069f20f4400ae0bb3ee830d34104ff8f7.tar.xz
crypto: testmgr - test in-place en/decryption with two sglists
As was established in the thread https://lore.kernel.org/linux-crypto/20220223080400.139367-1-gilad@benyossef.com/T/#u, many crypto API users doing in-place en/decryption don't use the same scatterlist pointers for the source and destination, but rather use separate scatterlists that point to the same memory. This case isn't tested by the self-tests, resulting in bugs. This is the natural usage of the crypto API in some cases, so requiring API users to avoid this usage is not reasonable. Therefore, update the self-tests to start testing this case. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'include/keys')
0 files changed, 0 insertions, 0 deletions