From: Patrick McHardy <kaber@trash.net>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-crypto@vger.kernel.org
Subject: Re: HIFN+IPsec crashes in current -git
Date: Tue, 19 Feb 2008 17:14:24 +0100 [thread overview]
Message-ID: <47BB0060.8080601@trash.net> (raw)
In-Reply-To: <47BAFF8F.7080602@trash.net>
Patrick McHardy wrote:
> Evgeniy Polyakov wrote:
>> Hi Patrick.
>>
>> On Wed, Feb 13, 2008 at 05:44:42PM +0300, Evgeniy Polyakov
>> (johnpol@2ka.mipt.ru) wrote:
>>> Any chance you can apply following patch and check output for correct
>>> and broken cases (it will produce 2 or 3 debug strings for each crypto
>>> operation)?
>>>
>>> diff --git a/drivers/crypto/hifn_795x.c b/drivers/crypto/hifn_795x.c
>>> index dfbf24c..b8b088d 100644
>>> --- a/drivers/crypto/hifn_795x.c
>>> +++ b/drivers/crypto/hifn_795x.c
>>> @@ -1558,6 +1558,23 @@ err_out_unmap:
>>> return err;
>>> }
>>>
>>> +static void hifn_dump_req(struct ablkcipher_request *req, const char
>>> *prefix)
>>> +{
>>> + int nbytes = (signed)req->nbytes;
>>> + struct scatterlist *src, *dst;
>>> + int idx = 0;
>>> +
>>> + printk("%s: nbytes: %u, ", prefix, nbytes);
>>> + while (nbytes > 0) {
>>> + src = &req->src[idx];
>>> + dst = &req->dst[idx];
>>> +
>>> + printk("%u/%u ", src->length, dst->length);
>>> + nbytes -= src->length;
>>
>> Ouch, forgot idx++;
>
>
> Unfortunately I'm unable to boot current -git, this time it
> hangs while trying to mount dm-crypt devices. The last output
> I get is:
>
> [ 15.148790] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_session: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_session: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_session: nbytes: 512, 512/512
> [ 15.148790] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.148837] hifn_setup_session: nbytes: 512, 512/512
> [ 15.148958] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.149085] hifn_setup_session: nbytes: 512, 512/512
> [ 15.149206] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.149332] hifn_setup_session: nbytes: 512, 512/512
> [ 15.149455] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.149582] hifn_setup_session: nbytes: 512, 512/512
> [ 15.149705] hifn_setup_crypto: nbytes: 512, 512/512
> [ 15.149871] hifn_setup_session: nbytes: 512, 512/512
>
> I'll try to narrow it down.
BTW, I also get this just before the HIFN debug output:
[ 14.695659] device-mapper: uevent: version 1.0.3
[ 14.697257] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18)
initialised: dm-devel@redhat.com
[ 15.137123] device-mapper: crypt: Selected cipher does not support IVs
Not sure if its related, but I don't get this when using software
crypto.
next prev parent reply other threads:[~2008-02-19 16:14 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 [this message]
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
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=47BB0060.8080601@trash.net \
--to=kaber@trash.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).