All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Dimitri Puzin <max@psycast.de>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>, linux-crypto@vger.kernel.org
Subject: Re: hifn_795x in Linux-2.6.27-rc7
Date: Wed, 24 Sep 2008 18:40:29 +0200	[thread overview]
Message-ID: <48DA6D7D.80705@trash.net> (raw)
In-Reply-To: <48D93028.20903@psycast.de>

Dimitri Puzin wrote:
> With this patch applied it still doesn't work as expected. The overflow
> messages are gone however syslog shows
> [  120.924266] hifn0: abort: c: 0, s: 1, d: 0, r: 0.
> when doing cryptsetup luksFormat as in original e-mail. At this point
> cryptsetup hangs and can't be killed with -SIGKILL. I've attached
> SysRq-t dump of this condition.

There are a few known problems left in the HIFN driver that I have
patches for but unfortunately didn't manage to clean them up and
submit them yet.

Looking at my queue, what's still broken is roughly:

    [HIFN]: Have HW invalidate src and dest descriptors after processing
   
    The descriptors need to be invalidated after processing for ring
    cleanup to work properly and to avoid using an old destination
    descriptor when the src and cmd descriptors are already set up
    and the dst descriptor isn't.
   
    Signed-off-by: Patrick McHardy <kaber@trash.net>

That one is actually probably OK but I didn't send it upstream yet because
I didn't finish all follow-up patches that depend on how this works.

Further:

    [HIFN]: Fix DMA setup

without a changelog :) IIRC the problem is that HIFN sets up each
DMA descriptor for the full request length, even though it should
only cover on SG entry. The result is memory corruption.

    [HIFN]: Don't copy src sg list

also without a changelog. I think this one was just an optimization,
the source descriptors don't have alignment or size restrictions and
thus we don't need to linearize it first.

    [HIFN]: Fix request context corruption
   
    HIFN uses the transform context to store per-request data, which breaks
    when more than one request is outstanding. Move per request members from
    struct hifn_context to a new struct hifn_request_context and convert
    the code to use this.

and:
  
    [HIFN]: Fix queue processing

again without a changelog. The problem this patch fixed was missing crypto
backlog handling, causing crashes with dm_crypt under load.

If someone is interested in picking this up I could send my old patches,
I probably won't manage to do it myself in the next time.


  parent reply	other threads:[~2008-09-24 16:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 17:39 hifn_795x in Linux-2.6.27-rc7 Dimitri Puzin
2008-09-23 16:55 ` Evgeniy Polyakov
2008-09-23 17:39   ` Evgeniy Polyakov
2008-09-23 18:06   ` Dimitri Puzin
2008-09-23 18:18     ` Evgeniy Polyakov
2008-09-23 21:55       ` David Miller
2008-09-24  2:53         ` Evgeniy Polyakov
2008-09-24  3:01           ` Herbert Xu
2008-09-24  3:05           ` David Miller
2008-10-12 12:14       ` Herbert Xu
2008-09-24 16:40     ` Patrick McHardy [this message]
2008-09-24 17:00       ` Evgeniy Polyakov
2008-09-24 17:13         ` Patrick McHardy
2008-09-24 17:16           ` Evgeniy Polyakov

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=48DA6D7D.80705@trash.net \
    --to=kaber@trash.net \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-crypto@vger.kernel.org \
    --cc=max@psycast.de \
    /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.