From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Raj Ammanur <rammanur@arista.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 0/5] crypto: Fix IPsec reordering caused by cryptd
Date: Fri, 24 Jun 2016 10:29:34 +0200 [thread overview]
Message-ID: <20160624082934.GR7698@gauss.secunet.com> (raw)
In-Reply-To: <20160621085321.GA21044@gondor.apana.org.au>
On Tue, Jun 21, 2016 at 04:53:21PM +0800, Herbert Xu wrote:
> Hi:
>
> I finally got around to working on this. I quickly gave up on the
> notion of hijacking the queued requests as we may end up overwhelming
> our caller.
>
> So the solution is the obvious one of using cryptd as long as there
> are requests queued there belonging to the same tfm. This is
> totally untested so please tread carefully.
Thanks for the patches!
I've tested them today and observed no problems with it,
so looks good :)
next prev parent reply other threads:[~2016-06-24 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 8:53 [PATCH 0/5] crypto: Fix IPsec reordering caused by cryptd Herbert Xu
2016-06-21 8:55 ` [PATCH 1/5] crypto: cryptd - Add helpers to check whether a tfm is queued Herbert Xu
2016-06-21 8:55 ` [PATCH 2/5] crypto: aesni - Fix cryptd reordering problem on gcm Herbert Xu
2016-06-21 8:55 ` [PATCH 3/5] crypto: ablk_helper - Fix cryptd reordering Herbert Xu
2016-06-21 8:55 ` [PATCH 4/5] crypto: ghash-clmulni " Herbert Xu
2016-06-21 8:55 ` [PATCH 5/5] crypto: ghash-ce " Herbert Xu
2016-06-24 8:29 ` Steffen Klassert [this message]
2016-06-24 8:40 ` [PATCH 0/5] crypto: Fix IPsec reordering caused by cryptd 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=20160624082934.GR7698@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=rammanur@arista.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