From: Anton Blanchard <anton@samba.org>
To: Marcelo Cerri <marcelo.cerri@canonical.com>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Paulo Flabiano Smorigo <pfsmorigo@linux.vnet.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 0/3] Fix crypto/vmx/p8_ghash memory corruption
Date: Thu, 29 Sep 2016 06:59:08 +1000 [thread overview]
Message-ID: <20160929065908.653ec5c2@kryten> (raw)
In-Reply-To: <1475080931-7926-1-git-send-email-marcelo.cerri@canonical.com>
Hi Marcelo
> This series fixes the memory corruption found by Jan Stancek in
> 4.8-rc7. The problem however also affects previous versions of the
> driver.
If it affects previous versions, please add the lines in the sign off to
get it into the stable kernels.
Anton
next prev parent reply other threads:[~2016-09-28 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 16:42 [PATCH 0/3] Fix crypto/vmx/p8_ghash memory corruption Marcelo Cerri
2016-09-28 16:42 ` [PATCH 1/3] crypto: ghash-generic - move common definitions to a new header file Marcelo Cerri
2016-09-28 16:42 ` [PATCH 2/3] crypto: vmx - Fix memory corruption caused by p8_ghash Marcelo Cerri
2016-09-28 16:42 ` [PATCH 3/3] crypto: vmx - Ensure ghash-generic is enabled Marcelo Cerri
2016-09-28 20:59 ` Anton Blanchard [this message]
2016-10-02 14:40 ` [PATCH 0/3] Fix crypto/vmx/p8_ghash memory corruption Herbert Xu
2016-10-03 12:08 ` Marcelo Cerri
2016-10-02 14:40 ` 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=20160929065908.653ec5c2@kryten \
--to=anton@samba.org \
--cc=davem@davemloft.net \
--cc=gcwilson@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marcelo.cerri@canonical.com \
--cc=paulus@samba.org \
--cc=pfsmorigo@linux.vnet.ibm.com \
/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).