From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@google.com>
Cc: stable@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH -stable] arm: crypto: reduce priority of bit-sliced AES cipher
Date: Sun, 19 Nov 2017 11:21:54 +0100 [thread overview]
Message-ID: <20171119102154.GA12993@kroah.com> (raw)
In-Reply-To: <20171117195027.88288-1-ebiggers@google.com>
On Fri, Nov 17, 2017 at 11:50:27AM -0800, Eric Biggers wrote:
> Hi,
>
> I'd like the following patch to be applied to stable for versions
> between 4.1 and 4.10 (inclusively).
>
> This is a minimal fix for a bug where arm32 kernels can use a much
> slower implementation of AES than is actually available, potentially
> forcing vendors to disable encryption on their devices.
>
> Min version is 4.1 because that was the first version to include the
> aes-ce algorithms.
>
> Max version is 4.10 because in 4.11, this bug was fixed incidentally as
> part of a complete rewrite of the bit-sliced AES implementation.
Thanks for the patch, now queued up.
greg k-h
next prev parent reply other threads:[~2017-11-19 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 19:50 [PATCH -stable] arm: crypto: reduce priority of bit-sliced AES cipher Eric Biggers
2017-11-17 20:07 ` Ard Biesheuvel
2017-11-19 10:21 ` Greg KH [this message]
2017-11-19 10:33 ` Patch "[PATCH -stable] arm: crypto: reduce priority of bit-sliced AES cipher" has been added to the 4.9-stable tree gregkh
2017-11-19 11:05 ` Patch "[PATCH -stable] arm: crypto: reduce priority of bit-sliced AES cipher" has been added to the 4.4-stable tree gregkh
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=20171119102154.GA12993@kroah.com \
--to=greg@kroah.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ebiggers@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.