Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jan Glauber <jang@linux.vnet.ibm.com>,
	linux-crypto <linux-crypto@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HMAC broken on s390
Date: Tue, 4 Dec 2007 09:25:11 +0100	[thread overview]
Message-ID: <20071204082511.GC23294@kernel.dk> (raw)
In-Reply-To: <20071203220900.GA8573@gondor.apana.org.au>

On Tue, Dec 04 2007, Herbert Xu wrote:
> On Mon, Dec 03, 2007 at 02:31:40PM +0100, Jan Glauber wrote:
> > Hi Herbert,
> > 
> > commit 788fefa33b0b50581585925c53c230a36af35d0e in cryptodev breaks hmac
> > on s390 du to the usage of sg_chain():
> > 
> > static inline void sg_chain(struct scatterlist *prv, unsigned int prv_nents,
> >                             struct scatterlist *sgl)
> > {
> > #ifndef ARCH_HAS_SG_CHAIN
> >         BUG();
> > #endif
> > 
> > ARCH_HAS_SG_CHAIN is false for s390 (and also for some other arch's).
> > 
> > What should we do with this?
> 
> Looks like we took a step backwards because the chaining I had
> before worked on all architectures :)
> 
> I suppose either we'll have to do our own chaining again or implement
> it for all architectures.  I'll look into this.

You should continue to do your own chaining if it's a requirement for
the driver/layer to function, until we get rid of ARCH_HAS_SG_CHAIN.
That'll happen when all archs are converted.

So don't rely on scatterlist helping you with chaining just yet, sorry.

-- 
Jens Axboe

  reply	other threads:[~2007-12-04  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 13:31 HMAC broken on s390 Jan Glauber
2007-12-03 22:09 ` Herbert Xu
2007-12-04  8:25   ` Jens Axboe [this message]
2007-12-04  8:51     ` 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=20071204082511.GC23294@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jang@linux.vnet.ibm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox