From: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
To: linux-crypto@vger.kernel.org
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: [RFC PATCH 0/3] Make rfc3686 template work with asynchronous block ciphers
Date: Fri, 28 Dec 2012 12:04:48 +0200 [thread overview]
Message-ID: <20121228100448.11073.25546.stgit@localhost6.localdomain6> (raw)
I'm not sure how this patchset should be dealt with (should 1st patch go
through different tree than 2nd and 3rd?), so therefore it's RFC.
Second patch makes rfc3686 template work with asynchronous block ciphers and
third patch changes aesni-intel to use this template. First patch fixed problem
in xfrm_algo found with help of 2nd and 3rd patches and without 1st patch
2nd patch breaks aes-ctr with IPSEC.
---
Jussi Kivilinna (3):
xfrm_algo: probe asynchronous block ciphers instead of synchronous
crypto: ctr - make rfc3686 asynchronous block cipher
crypto: aesni-intel - remove rfc3686(ctr(aes)), utilize rfc3686 from ctr-module instead
arch/x86/crypto/aesni-intel_glue.c | 37 --------
crypto/ctr.c | 173 +++++++++++++++++++++++-------------
crypto/tcrypt.c | 4 +
crypto/tcrypt.h | 1
net/xfrm/xfrm_algo.c | 3 -
5 files changed, 116 insertions(+), 102 deletions(-)
next reply other threads:[~2012-12-28 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 10:04 Jussi Kivilinna [this message]
2012-12-28 10:04 ` [RFC PATCH 1/3] xfrm_algo: probe asynchronous block ciphers instead of synchronous Jussi Kivilinna
2012-12-28 10:04 ` [RFC PATCH 2/3] crypto: ctr - make rfc3686 asynchronous block cipher Jussi Kivilinna
2012-12-28 10:05 ` [RFC PATCH 3/3] crypto: aesni-intel - remove rfc3686(ctr(aes)), utilize rfc3686 from ctr-module instead Jussi Kivilinna
2012-12-28 22:42 ` [RFC PATCH 0/3] Make rfc3686 template work with asynchronous block ciphers Herbert Xu
2012-12-28 23:23 ` David Miller
2012-12-29 0:08 ` Herbert Xu
2013-01-07 7:00 ` Steffen Klassert
2013-01-07 20:18 ` Herbert Xu
2013-01-08 7:04 ` Steffen Klassert
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=20121228100448.11073.25546.stgit@localhost6.localdomain6 \
--to=jussi.kivilinna@mbnet.fi \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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