mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
	herbert@gondor.apana.org.au, ard.biesheuvel@linaro.org
Subject: [GIT PULL] arm64 regression fix for 4.18
Date: Thu, 2 Aug 2018 13:01:17 +0100	[thread overview]
Message-ID: <20180802120117.GB14419@arm.com> (raw)

Hi Linus,

Ard found a nasty arm64 regression in 4.18 where the AES ghash/gcm code
doesn't notify the kernel about its use of the vector registers, therefore
potentially corrupting live user state. The fix is straightforward and
Herbert agreed for it to go via arm64.

Please pull.

Thanks,

Will

--->8

The following changes since commit acb1872577b346bd15ab3a3f8dff780d6cca4b70:

  Linux 4.18-rc7 (2018-07-29 14:44:52 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to c7513c2a2714204d3588ecaa170ae628fd0d217e:

  crypto/arm64: aes-ce-gcm - add missing kernel_neon_begin/end pair (2018-07-31 13:20:30 +0100)

----------------------------------------------------------------
arm64 regression fix

- Fix potential clobbering of user vector register state by AES ghash code

----------------------------------------------------------------
Ard Biesheuvel (1):
      crypto/arm64: aes-ce-gcm - add missing kernel_neon_begin/end pair

 arch/arm64/crypto/ghash-ce-glue.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

                 reply	other threads:[~2018-08-02 12:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180802120117.GB14419@arm.com \
    --to=will.deacon@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome