All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-crypto@vger.kernel.org
Subject: Re: HIFN+IPsec crashes in current -git
Date: Thu, 21 Feb 2008 16:29:54 +0100	[thread overview]
Message-ID: <47BD98F2.4080305@trash.net> (raw)
In-Reply-To: <47BD8D93.3070906@trash.net>

Patrick McHardy wrote:
> Evgeniy Polyakov wrote:
>> On Thu, Feb 21, 2008 at 03:20:45PM +0100, Patrick McHardy 
>> (kaber@trash.net) wrote:
>>> Almost I guess :) There are similar loops in hifn_setup_session().
>>> Additionally we need to check that the return value of ablkcipher_walk()
>>> is not a negative errno code.
>>
>> Yep. Kind of this one:
> 
> Thanks, I'll give it a try. It includes one chunk I missed when
> trying this myself, which might explain the problems I saw
> afterwards.

Unfortunately still no luck. I got an error from ablkcipher_add()
because of this condition:

     if (drest < size || size > nbytes)

with size=124 any nbytes=112. After changing ablkcipher_walk():

- unsigned slen = src->length - offset
+ unsigned slen = min(src->length, nbytes) - offset;

the error went away and I got a silent crash (at least
nothing was logged over netconsole).

It also looks like at least two more changes are needed:

- hifn_setup_session does:

                 if (src->length & (blocksize - 1) ||
..
                                 dst->length & (blocksize - 1) ||

                         ctx->walk.flags |= ASYNC_FLAGS_MISALIGNED;

which looks like it should use min(length, nbytes).

- further down it uses dst->length in the last while-loop,
   which seems to need a similar change.

  reply	other threads:[~2008-02-21 15:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 13:17 HIFN+IPsec crashes in current -git Patrick McHardy
2008-02-13 14:44 ` Evgeniy Polyakov
2008-02-14  9:30   ` Evgeniy Polyakov
2008-02-19 16:10     ` Patrick McHardy
2008-02-19 16:14       ` Patrick McHardy
2008-02-19  6:23 ` Herbert Xu
2008-02-19 16:27   ` Patrick McHardy
2008-02-20  0:53     ` Herbert Xu
2008-02-20 12:33       ` Patrick McHardy
2008-02-20 13:19         ` Evgeniy Polyakov
2008-02-20 17:29           ` Herbert Xu
2008-02-20 17:26         ` Herbert Xu
2008-02-21  9:10           ` Evgeniy Polyakov
2008-02-21 14:10             ` Herbert Xu
2008-02-21 14:18               ` Evgeniy Polyakov
2008-02-21 14:20                 ` Patrick McHardy
2008-02-21 14:37                   ` Evgeniy Polyakov
2008-02-21 14:41                     ` Patrick McHardy
2008-02-21 15:29                       ` Patrick McHardy [this message]
2008-02-21 15:31                         ` Patrick McHardy
2008-02-22 12:42                         ` Evgeniy Polyakov
2008-02-22 13:53                           ` Patrick McHardy
2008-02-22  2:27               ` Test AES-CCM mode via IPSec (NETKEY) Loc Ho
2008-02-22  5:45                 ` Herbert Xu
2008-03-13 17:34                   ` Loc Ho
2008-03-14  1:12                     ` Herbert Xu
2008-04-04 22:37                     ` Joy Latten
2008-04-04 23:08                       ` Loc Ho

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=47BD98F2.4080305@trash.net \
    --to=kaber@trash.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=johnpol@2ka.mipt.ru \
    --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.