From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH 2/4] crypto: DRBG - use aligned buffers
Date: Mon, 13 Jun 2016 12:10:03 +0200 [thread overview]
Message-ID: <2604191.AVFi5UBCGh@tauon.atsec.com> (raw)
In-Reply-To: <20160613093714.GA7634@gondor.apana.org.au>
Am Montag, 13. Juni 2016, 17:37:14 schrieb Herbert Xu:
Hi Herbert,
> On Fri, Jun 10, 2016 at 07:56:57AM +0200, Stephan Mueller wrote:
> > Hardware cipher implementation may require aligned buffers. All buffers
> > that potentially are processed with a cipher are now aligned.
> >
> > At the time of the allocation of the memory, we have not yet allocated
> > the cipher implementations. Hence, we cannot obtain the alignmask for
> > the used cipher yet. Therefore, the DRBG code uses an alignment which
> > should satisfy all cipher implementations.
>
> Why not change it so that you allocate these buffers after you
> have obtained the tfm object? An alignment of 8 doesn't work for
> padlock at least, but then again the padlock driver doesn't support
> CTR so it's no big deal.
>
> I think if you are going to worry about alignment then let's do it
> properly and use the actual alignment required.
Will do.
>
> Cheers,
Ciao
Stephan
next prev parent reply other threads:[~2016-06-13 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 5:55 [PATCH 0/4] crypto: CTR DRBG - performance improvements Stephan Mueller
2016-06-10 5:56 ` [PATCH 1/4] crypto: CTR DRBG - use CTR AES instead of ECB AES Stephan Mueller
2016-06-10 5:56 ` [PATCH 2/4] crypto: DRBG - use aligned buffers Stephan Mueller
2016-06-13 9:37 ` Herbert Xu
2016-06-13 10:10 ` Stephan Mueller [this message]
2016-06-10 5:57 ` [PATCH 3/4] crypto: CTR DRBG - use full CTR AES for update Stephan Mueller
2016-06-10 5:58 ` [PATCH 4/4] crypto: CTR DRBG - avoid duplicate maintenance of key Stephan Mueller
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=2604191.AVFi5UBCGh@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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 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.