Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Herbert Xu" <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, stable@kernel.org
Subject: Re: geode: fix not inplace encryption
Date: Tue, 6 Nov 2007 14:30:40 -0700	[thread overview]
Message-ID: <20071106213040.GA30907@cosmic.amd.com> (raw)
In-Reply-To: <20071106200155.GA28183@Chamillionaire.breakpoint.cc>

On 06/11/07 21:01 +0100, Sebastian Siewior wrote:
> Currently the Geode AES module fails to encrypt or decrypt if
> the coherent bits are not set what is currently the case if the
> encryption does not occur inplace. However, the encryption works 
> on my Geode machine _only_ if the coherent bits are always set.
> 
> Cc: Jordan Crouse <jordan.crouse@amd.com>
> Signed-off-by: Sebastian Siewior <sebastian@breakpoint.cc>

Acked-by: Jordan Crouse <jordan.crouse@amd.com>

Anything in the cache is suspect - turning on coherency is the best plan
to be rock solid.

> ---
>  drivers/crypto/geode-aes.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/crypto/geode-aes.c b/drivers/crypto/geode-aes.c
> index f2d4fba..0ca92d4 100644
> --- a/drivers/crypto/geode-aes.c
> +++ b/drivers/crypto/geode-aes.c
> @@ -81,8 +81,7 @@ geode_aes_crypt(struct geode_aes_op *op)
>  	 * we don't need to worry
>  	 */
>  
> -	if (op->src == op->dst)
> -		flags |= (AES_CTRL_DCA | AES_CTRL_SCA);
> +	flags |= (AES_CTRL_DCA | AES_CTRL_SCA);
>  
>  	if (op->dir == AES_DIR_ENCRYPT)
>  		flags |= AES_CTRL_ENCRYPT;
> -- 
> 1.5.3.4
> 
> 
> 

-- 
Jordan Crouse
Systems Software Development Engineer 
Advanced Micro Devices, Inc.

  reply	other threads:[~2007-11-06 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 20:01 [PATCH] [crypto] geode: fix not inplace encryption Sebastian Siewior
2007-11-06 21:30 ` Jordan Crouse [this message]
2007-11-10 11:39   ` Herbert Xu
2007-11-10 20:58     ` Sebastian Siewior
2007-11-11 11:05       ` 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=20071106213040.GA30907@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox