From: Marek Vasut <marex@denx.de>
To: Mathias Krause <minipli@googlemail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org,
Chandramouli Narayanan <mouli@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/3] crypto: x86/sha1 - regression and other fixes
Date: Mon, 24 Mar 2014 21:19:44 +0100 [thread overview]
Message-ID: <201403242119.44692.marex@denx.de> (raw)
In-Reply-To: <1395677439-7478-1-git-send-email-minipli@googlemail.com>
On Monday, March 24, 2014 at 05:10:36 PM, Mathias Krause wrote:
> The recent addition of the AVX2 variant of the SHA1 hash function wrongly
> disabled the AVX variant by introducing a flaw in the feature test. Fixed
> in patch 1.
>
> The alignment calculations of the AVX2 assembler implementation are
> questionable, too. Especially the page alignment of the stack pointer is
> broken in multiple ways. Fixed in patch 2. In patch 3 another issue for
> code alignment is fixed.
>
> Please apply!
Nice,
Reviewed-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-03-24 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 16:10 [PATCH 0/3] crypto: x86/sha1 - regression and other fixes Mathias Krause
2014-03-24 16:10 ` [PATCH 1/3] crypto: x86/sha1 - re-enable the AVX variant Mathias Krause
2014-03-24 16:10 ` [PATCH 2/3] crypto: x86/sha1 - fix stack alignment of AVX2 variant Mathias Krause
2014-03-24 16:10 ` [PATCH 3/3] crypto: x86/sha1 - reduce size of the AVX2 asm implementation Mathias Krause
2014-03-24 17:04 ` [PATCH 0/3] crypto: x86/sha1 - regression and other fixes H. Peter Anvin
2014-03-24 17:29 ` chandramouli narayanan
2014-03-25 7:55 ` Mathias Krause
2014-03-24 17:31 ` H. Peter Anvin
2014-03-24 20:19 ` Marek Vasut [this message]
2014-03-25 12:44 ` 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=201403242119.44692.marex@denx.de \
--to=marex@denx.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=mouli@linux.intel.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 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.