Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Harald Welte <HaraldWelte@viatech.com>
To: Phil Sutter <phil@nwl.cc>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, Chuck Ebbert <cebbert@redhat.com>,
	Nico Erfurth <ne@erfurth.eu>, Michal Ludvig <michal@logix.cz>
Subject: Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
Date: Wed, 8 Dec 2010 08:08:13 +0800	[thread overview]
Message-ID: <20101208000813.GC10791@prithivi.gnumonks.org> (raw)
In-Reply-To: <20101207134057.GB24946@orbit.nwl.cc>

Sorry for jumping into this thread so late.

I am almost constantly on business travel (without any VIA system with me), so
I cannot try to reproduce the problem.  It probably has never shown up before
since my typical test case is dm-crypt and there you will of course never see
any unaligned buffers for encryption.

I'm returning home on December 11, and hopfeully can do some testing at
that time.

Is there a list of machines (/proc/cpuinfo) on which the problem has shown up
so far?

Regards,
	Harald
-- 
- Harald Welte <HaraldWelte@viatech.com>	    http://linux.via.com.tw/

  reply	other threads:[~2010-12-08  0:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 17:50 [PATCH] crypto: padlock: fix for non-64byte aligned data Phil Sutter
2010-11-04 18:46 ` Herbert Xu
2010-11-05 14:12   ` Phil Sutter
2010-12-02  6:14     ` Herbert Xu
2010-12-07 10:41       ` Phil Sutter
2010-12-07 11:39         ` Herbert Xu
2010-12-07 13:40           ` Phil Sutter
2010-12-08  0:08             ` Harald Welte [this message]
2010-12-08  1:52               ` 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=20101208000813.GC10791@prithivi.gnumonks.org \
    --to=haraldwelte@viatech.com \
    --cc=cebbert@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=michal@logix.cz \
    --cc=ne@erfurth.eu \
    --cc=phil@nwl.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