mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <HaraldWelte@viatech.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [patch 0/3] crypto: padlock-aes: enable on VIA Nano
Date: Thu, 11 Jun 2009 00:48:53 +0800	[thread overview]
Message-ID: <20090610164853.GI4131@prithivi.gnumonks.org> (raw)
In-Reply-To: <20090609184203.GA22084@Chamillionaire.breakpoint.cc>

Hi all,

On Tue, Jun 09, 2009 at 08:42:03PM +0200, Sebastian Andrzej Siewior wrote:
> * Chuck Ebbert | 2009-06-09 10:35:33 [-0400]:
> 
> >The VIA Nano has a bug that makes the padlock unit fetch extra data
> >during encryption operations. Add workarounds for that, and enable
> >the driver on x86_64.
> Nice. The X86_64 padlock will make it mainline in next merge window so
> I'm asking you kindly to rebase it against Herbert's cryptodev tree [0].
> 
> I guess the bug can trigger on 32bit if you boot the affected 64bit CPU
> in 32bit mode? I'm not sure if it is better to send this patches via
> stable tree _or_ deactivate the padlock on affected CPUs.

I have now re-confirmed the errata with VIA/Centaur guys, and it seems correct.
Also, reviewing [but not testing] the patch, it looks correct to me.

The check for stepping '2' is also correct, as stepping 3 no longer has this
issue.

Chuck, I'd be more than thankful if you could rebase and resubmit as requested.
If not, please drop me a not so i can put it on my todo list.

Acked-by: HaraldWelte <HaraldWelte@viatech.com>
-- 
- Harald Welte <HaraldWelte@viatech.com>	    http://linux.via.com.tw/
============================================================================
VIA Free and Open Source Software Liaison

  reply	other threads:[~2009-06-10 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 14:35 Chuck Ebbert
2009-06-09 14:36 ` [patch 1/3] crypto: padlock-aes: work around Nano CPU errata in ECB mode Chuck Ebbert
2009-06-09 14:37 ` [patch 2/3] crypto: padlock-aes: work around Nano CPU errata in CBC mode Chuck Ebbert
2009-06-09 14:39 ` [patch 3/3] crypto: padlock-aes: enable on 64-bit kernels Chuck Ebbert
2009-06-09 18:47   ` Sebastian Andrzej Siewior
2009-06-09 16:29 ` [patch 0/3] crypto: padlock-aes: enable on VIA Nano Chuck Ebbert
2009-06-09 18:42 ` Sebastian Andrzej Siewior
2009-06-10 16:48   ` Harald Welte [this message]
2009-06-09 18:45 ` Harald Welte

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=20090610164853.GI4131@prithivi.gnumonks.org \
    --to=haraldwelte@viatech.com \
    --cc=cebbert@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian@breakpoint.cc \
    /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

all inboxes | Powered by JetHome®