diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-10-25 18:40:08 +0100 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2020-10-25 18:40:08 +0100 |
commit | 91f28da8c9a054286d6917ce191349455c479478 (patch) | |
tree | e095a831ada79f835d1d9310df529007665a498e /security/safesetid/securityfs.c | |
parent | Merge tag 'block-5.10-2020-10-24' of git://git.kernel.dk/linux-block (diff) | |
parent | random32: add a selftest for the prandom32 code (diff) | |
download | linux-91f28da8c9a054286d6917ce191349455c479478.tar.xz linux-91f28da8c9a054286d6917ce191349455c479478.zip |
Merge tag '20201024-v4-5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/prandom
Pull random32 updates from Willy Tarreau:
"Make prandom_u32() less predictable.
This is the cleanup of the latest series of prandom_u32
experimentations consisting in using SipHash instead of Tausworthe to
produce the randoms used by the network stack.
The changes to the files were kept minimal, and the controversial
commit that used to take noise from the fast_pool (f227e3ec3b5c) was
reverted. Instead, a dedicated "net_rand_noise" per_cpu variable is
fed from various sources of activities (networking, scheduling) to
perturb the SipHash state using fast, non-trivially predictable data,
instead of keeping it fully deterministic. The goal is essentially to
make any occasional memory leakage or brute-force attempt useless.
The resulting code was verified to be very slightly faster on x86_64
than what is was with the controversial commit above, though this
remains barely above measurement noise. It was also tested on i386 and
arm, and build- tested only on arm64"
Link: https://lore.kernel.org/netdev/20200808152628.GA27941@SDF.ORG/
* tag '20201024-v4-5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/prandom:
random32: add a selftest for the prandom32 code
random32: add noise from network and scheduling activity
random32: make prandom_u32() output unpredictable
Diffstat (limited to 'security/safesetid/securityfs.c')
0 files changed, 0 insertions, 0 deletions