aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2018-06-21 22:58:01 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2018-06-22 04:09:39 +0200
commit7e8817466f02b215d7714cb0f179a6f79f05b98b (patch)
tree87d08cfba555c3fa7d73067ec69dd49ef7da2869
parentmain: test poly1305 before chacha20poly1305 (diff)
downloadwireguard-monolithic-historical-7e8817466f02b215d7714cb0f179a6f79f05b98b.tar.xz
wireguard-monolithic-historical-7e8817466f02b215d7714cb0f179a6f79f05b98b.zip
poly1305: give linker the correct constant data section size
Otherwise these constants will be merged wrong or excluded, and we'll wind up with wrong calculations. While bfd (the normal kernel linker) doesn't seem to mind, recent versions of gold do bad things.
-rw-r--r--src/crypto/poly1305-x86_64.S2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/crypto/poly1305-x86_64.S b/src/crypto/poly1305-x86_64.S
index 3ab21ea..7c1b736 100644
--- a/src/crypto/poly1305-x86_64.S
+++ b/src/crypto/poly1305-x86_64.S
@@ -7,7 +7,7 @@
#include <linux/linkage.h>
-.section .rodata.cst192.Lconst, "aM", @progbits, 32
+.section .rodata.cst192.Lconst, "aM", @progbits, 192
.align 64
.Lconst:
.long 0x0ffffff,0,0x0ffffff,0,0x0ffffff,0,0x0ffffff,0