summaryrefslogtreecommitdiff
path: root/arch/c6x
diff options
context:
space:
mode:
authorStephan Müller <smueller@chronox.de>2021-11-21 17:14:20 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-01-27 12:54:12 +0300
commit8a6371d84c5f80218ae35f31f26a5fb230ef4dba (patch)
treee61ba5fa03b2d901ed32f8c030be6193aa2e24b4 /arch/c6x
parent240cf5d3cb5e4d3eb1b7abc83b54563fe992d306 (diff)
downloadlinux-8a6371d84c5f80218ae35f31f26a5fb230ef4dba.tar.xz
crypto: jitter - consider 32 LSB for APT
[ Upstream commit 552d03a223eda3df84526ab2c1f4d82e15eaee7a ] The APT compares the current time stamp with a pre-set value. The current code only considered the 4 LSB only. Yet, after reviews by mathematicians of the user space Jitter RNG version >= 3.1.0, it was concluded that the APT can be calculated on the 32 LSB of the time delta. Thi change is applied to the kernel. This fixes a bug where an AMD EPYC fails this test as its RDTSC value contains zeros in the LSB. The most appropriate fix would have been to apply a GCD calculation and divide the time stamp by the GCD. Yet, this is a significant code change that will be considered for a future update. Note, tests showed that constantly the GCD always was 32 on these systems, i.e. the 5 LSB were always zero (thus failing the APT since it only considered the 4 LSB for its calculation). Signed-off-by: Stephan Mueller <smueller@chronox.de> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/c6x')
0 files changed, 0 insertions, 0 deletions