From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] crypto: arm64/chacha - fix chacha_4block_xor_neon() for big endian
Date: Sat, 23 Feb 2019 10:21:22 +0100 [thread overview]
Message-ID: <CAKv+Gu-4dwMsukX9jf9U0GfCOtd7cGfaRfSeJ+xL+4cqBAsDmg@mail.gmail.com> (raw)
In-Reply-To: <20190223065408.6279-2-ebiggers@kernel.org>
On Sat, 23 Feb 2019 at 07:54, Eric Biggers <ebiggers@kernel.org> wrote:
>
> From: Eric Biggers <ebiggers@google.com>
>
> The change to encrypt a fifth ChaCha block using scalar instructions
> caused the chacha20-neon, xchacha20-neon, and xchacha12-neon self-tests
> to start failing on big endian arm64 kernels. The bug is that the
> keystream block produced in 32-bit scalar registers is directly XOR'd
> with the data words, which are loaded and stored in native endianness.
> Thus in big endian mode the data bytes end up XOR'd with the wrong
> bytes. Fix it by byte-swapping the keystream words in big endian mode.
>
> Fixes: 2fe55987b262 ("crypto: arm64/chacha - use combined SIMD/ALU routine for more speed")
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/crypto/chacha-neon-core.S | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/crypto/chacha-neon-core.S b/arch/arm64/crypto/chacha-neon-core.S
> index 021bb9e9784b2..bfb80e10ff7b0 100644
> --- a/arch/arm64/crypto/chacha-neon-core.S
> +++ b/arch/arm64/crypto/chacha-neon-core.S
> @@ -532,6 +532,10 @@ ENTRY(chacha_4block_xor_neon)
> add v3.4s, v3.4s, v19.4s
> add a2, a2, w8
> add a3, a3, w9
> +CPU_BE( rev a0, a0 )
> +CPU_BE( rev a1, a1 )
> +CPU_BE( rev a2, a2 )
> +CPU_BE( rev a3, a3 )
>
> ld4r {v24.4s-v27.4s}, [x0], #16
> ld4r {v28.4s-v31.4s}, [x0]
> @@ -552,6 +556,10 @@ ENTRY(chacha_4block_xor_neon)
> add v7.4s, v7.4s, v23.4s
> add a6, a6, w8
> add a7, a7, w9
> +CPU_BE( rev a4, a4 )
> +CPU_BE( rev a5, a5 )
> +CPU_BE( rev a6, a6 )
> +CPU_BE( rev a7, a7 )
>
> // x8[0-3] += s2[0]
> // x9[0-3] += s2[1]
> @@ -569,6 +577,10 @@ ENTRY(chacha_4block_xor_neon)
> add v11.4s, v11.4s, v27.4s
> add a10, a10, w8
> add a11, a11, w9
> +CPU_BE( rev a8, a8 )
> +CPU_BE( rev a9, a9 )
> +CPU_BE( rev a10, a10 )
> +CPU_BE( rev a11, a11 )
>
> // x12[0-3] += s3[0]
> // x13[0-3] += s3[1]
> @@ -586,6 +598,10 @@ ENTRY(chacha_4block_xor_neon)
> add v15.4s, v15.4s, v31.4s
> add a14, a14, w8
> add a15, a15, w9
> +CPU_BE( rev a12, a12 )
> +CPU_BE( rev a13, a13 )
> +CPU_BE( rev a14, a14 )
> +CPU_BE( rev a15, a15 )
>
> // interleave 32-bit words in state n, n+1
> ldp w6, w7, [x2], #64
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-23 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 6:54 [PATCH 0/2] crypto: arm64/chacha - fix for big endian Eric Biggers
2019-02-23 6:54 ` [PATCH 1/2] crypto: arm64/chacha - fix chacha_4block_xor_neon() " Eric Biggers
2019-02-23 9:21 ` Ard Biesheuvel [this message]
2019-02-23 6:54 ` [PATCH 2/2] crypto: arm64/chacha - fix hchacha_block_neon() " Eric Biggers
2019-02-23 9:24 ` Ard Biesheuvel
2019-02-28 6:38 ` [PATCH 0/2] crypto: arm64/chacha - fix " Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKv+Gu-4dwMsukX9jf9U0GfCOtd7cGfaRfSeJ+xL+4cqBAsDmg@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).