crypto: tcrypt - avoid signed overflow in byte count
authorArd Biesheuvel <ardb@kernel.org>
Tue, 8 Dec 2020 14:34:41 +0000 (15:34 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 7 Mar 2021 11:34:11 +0000 (12:34 +0100)
commited51ffe96abcdd5c39fb55ac0e1b2242b097d7e4
treeb1740b40ff0e1718d5a902b224ebe1b66063eb98
parentbb5e204b6b9818c2e2ff8f28a941cf537d5bdf4d
crypto: tcrypt - avoid signed overflow in byte count

[ Upstream commit 303fd3e1c771077e32e96e5788817f025f0067e2 ]

The signed long type used for printing the number of bytes processed in
tcrypt benchmarks limits the range to -/+ 2 GiB, which is not sufficient
to cover the performance of common accelerated ciphers such as AES-NI
when benchmarked with sec=1. So switch to u64 instead.

While at it, fix up a missing printk->pr_cont conversion in the AEAD
benchmark.

Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Sasha Levin <sashal@kernel.org>
crypto/tcrypt.c