summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/bpf_testmod
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2024-08-28 15:49:32 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2024-09-13 17:28:35 +0200
commit7fe5b3e4e7a61f3640d7645c434ac8c982f1388e (patch)
tree10dc19ffe6bd21bd25dc432d4654a0598e484237 /tools/testing/selftests/bpf/bpf_testmod
parent6fd13b282f62bd840f2410692deaa23a42fd91fa (diff)
selftests: vDSO: open code basic chacha instead of linking to libsodium
Linking to libsodium makes building this test annoying in cross compilation environments and is just way too much. Since this is just a basic correctness test, simply open code a simple, unoptimized, dumb chacha, rather than linking to libsodium. This also fixes a correctness issue on big endian systems. The kernel's random.c doesn't bother doing a le32_to_cpu operation on the random bytes that are passed as the key, and consequently neither does vgetrandom-chacha.S. However, libsodium's chacha _does_ do this, since it takes the key as an array of bytes. This meant that the test was broken on big endian systems, which this commit rectifies. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'tools/testing/selftests/bpf/bpf_testmod')
0 files changed, 0 insertions, 0 deletions