From: Huang Ying <ying.huang@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: roel kluin <roel.kluin@gmail.com>,
Sebastian Siewior <linux-crypto@ml.breakpoint.cc>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH crypto -v4 2/2] AES-NI: Add support to Intel AES-NI instructions for x86_64 platform
Date: Fri, 16 Jan 2009 11:37:25 +0800 [thread overview]
Message-ID: <1232077045.13948.14.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20090116032639.GA10390@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Fri, 2009-01-16 at 11:26 +0800, Herbert Xu wrote:
> On Fri, Jan 16, 2009 at 10:37:02AM +0800, Huang Ying wrote:
> >
> > But after checking blkcipher_walk_done() in 2.6.28, If input argument
> > err != 0 and walk->flags & BLKCIPHER_WALK_SLOW != 0, when
> > blkcipher_walk_done() return non-zero, walk->nbytes != 0. So I think it
> > is a little fragile to use walk->nbytes == 0 indicate error.
>
> Right, that's a bug. Although this case shouldn't occur unless
> wer have a buggy algorithm (that's why it's a WARN_ON). But as
> we're handling it anyway, we should ensure that the result is sane.
>
> crypt: blkcipher - Fix WARN_ON handling in walk_done
>
> When we get left-over bits from a slow walk, it means that the
> underlying cipher has gone troppo. However, as we're handling
> that case we should ensure that the caller terminates the walk.
>
> This patch does this by setting walk->nbytes to zero.
>
> Reported-by: Huang Ying <ying.huang@intel.com>
I think Roel Kluin is the real reporter.
Best Regards,
Huang Ying
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-16 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 8:28 [PATCH crypto -v4 2/2] AES-NI: Add support to Intel AES-NI instructions for x86_64 platform Huang Ying
[not found] ` <25e057c00901150147t570d8ab6g3b2b99c60f10c3c2@mail.gmail.com>
2009-01-16 1:20 ` Huang Ying
2009-01-16 1:53 ` Herbert Xu
2009-01-16 2:37 ` Huang Ying
2009-01-16 3:26 ` Herbert Xu
2009-01-16 3:37 ` Huang Ying [this message]
2009-01-16 3:41 ` 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=1232077045.13948.14.camel@yhuang-dev.sh.intel.com \
--to=ying.huang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
/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