From: "Stephan Müller" <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, harsh@chelsio.com,
jonathan.cameron@huawei.com
Subject: Re: [PATCH] crypto: AF_ALG - inline IV support
Date: Sun, 21 Jan 2018 13:14:30 +0100 [thread overview]
Message-ID: <2165621.DHQGk8sIp3@positron.chronox.de> (raw)
In-Reply-To: <1972650.zFSS3VNpIS@tauon.chronox.de>
Hi Herbert,
I tried to summarize the use cases of the AIO support at [1].
The use case covering the inline IV support is documented in section [2]. It
naturally would depend on this patch to be accepted. What is your take on this
use case?
What is your take on the issue outlined at [3]? Should the affected drivers be
updated?
Thanks
Stephan
[1] https://github.com/smuellerDD/libkcapi/commit/
29132075b8f045f3f92367c0190add81ccf5da11
[2] https://github.com/smuellerDD/libkcapi/commit/
29132075b8f045f3f92367c0190add81ccf5da11#diff-
dce7a00cbc610df94f0dc27eb769d01dR644
[3] https://github.com/smuellerDD/libkcapi/commit/
29132075b8f045f3f92367c0190add81ccf5da11#diff-
dce7a00cbc610df94f0dc27eb769d01dR575
next prev parent reply other threads:[~2018-01-21 12:14 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 13:21 [RFC] AF_ALG AIO and IV Stephan Mueller
2018-01-15 9:35 ` [PATCH] crypto: AF_ALG - inline IV support Stephan Mueller
2018-01-21 12:14 ` Stephan Müller [this message]
2018-01-23 11:02 ` Harsh Jain
2018-01-30 8:27 ` [PATCH] crypto: AF_ALG AIO - lock context IV Stephan Müller
2018-01-30 14:04 ` Stephan Mueller
2018-01-30 15:51 ` Jonathan Cameron
2018-01-31 12:29 ` Jonathan Cameron
2018-02-01 9:35 ` Gilad Ben-Yossef
2018-02-01 9:46 ` Stephan Mueller
2018-02-01 10:06 ` Gilad Ben-Yossef
2018-02-01 10:15 ` Stephan Mueller
2018-02-01 10:04 ` Stephan Mueller
2018-02-01 10:07 ` Gilad Ben-Yossef
2018-02-01 10:25 ` Jonathan Cameron
2018-02-01 10:55 ` Harsh Jain
2018-02-07 7:42 ` [PATCH v2 0/4] crypto: AF_ALG AIO improvements Stephan Müller
2018-02-07 7:43 ` [PATCH v2 1/4] crypto: AF_ALG AIO - lock context IV Stephan Müller
2018-02-07 7:43 ` [PATCH v2 2/4] crypto: AF_ALG - inline IV support Stephan Müller
2018-02-07 13:54 ` Jonathan Cameron
2018-02-07 14:01 ` Stephan Müller
2018-02-07 7:43 ` [PATCH v2 3/4] crypto: AF_ALG - allow driver to serialize IV access Stephan Müller
2018-02-07 7:44 ` [PATCH v2 4/4] crypto: add CRYPTO_TFM_REQ_PARALLEL flag Stephan Müller
2018-02-07 12:48 ` Stephan Mueller
2018-02-07 15:39 ` Jonathan Cameron
2018-02-07 15:43 ` Stephan Mueller
2018-02-07 16:14 ` Jonathan Cameron
2018-02-07 16:25 ` Stephan Mueller
2018-02-07 8:52 ` [PATCH v2 0/4] crypto: AF_ALG AIO improvements Harsh Jain
2018-02-07 15:37 ` Jonathan Cameron
2018-02-09 22:02 ` [PATCH v3 " Stephan Müller
2018-02-09 22:03 ` [PATCH v3 1/4] crypto: AF_ALG AIO - lock context IV Stephan Müller
2018-02-14 5:43 ` Harsh Jain
2018-02-14 12:52 ` Stephan Mueller
2018-02-15 5:30 ` Harsh Jain
2018-02-15 6:28 ` Stephan Mueller
2018-02-15 7:03 ` Harsh Jain
2018-02-15 7:17 ` Stephan Mueller
2018-02-15 11:38 ` Harsh Jain
2018-02-15 11:45 ` Stephan Mueller
2018-02-15 12:45 ` Harsh Jain
2018-02-15 13:04 ` Stephan Mueller
2018-02-15 13:26 ` Jeffrey Walton
2018-02-15 18:09 ` Stephan Mueller
2018-02-09 22:03 ` [PATCH v3 2/4] crypto: AF_ALG - inline IV support Stephan Müller
2018-02-09 22:04 ` [PATCH v3 3/4] crypto: AF_ALG - allow driver to serialize IV access Stephan Müller
2018-02-09 22:04 ` [PATCH v3 4/4] crypto: add CRYPTO_TFM_REQ_IV_SERIALIZE flag Stephan Müller
2018-02-14 5:50 ` Harsh Jain
2018-02-14 12:47 ` Stephan Mueller
2018-01-22 14:11 ` [PATCH] crypto: AF_ALG - inline IV support Jonathan Cameron
2018-01-22 14:30 ` Stephan Mueller
2018-01-22 14:52 ` Jonathan Cameron
2018-01-15 9:39 ` [RFC] AF_ALG AIO and IV Stephan Mueller
2018-01-15 11:05 ` Jonathan Cameron
2018-01-15 12:07 ` Stephan Mueller
2018-01-15 12:59 ` Jonathan Cameron
2018-01-15 13:15 ` Stephan Mueller
2018-01-15 14:25 ` Jonathan Cameron
2018-01-15 14:31 ` Stephan Mueller
2018-01-15 14:42 ` Jonathan Cameron
2018-01-16 6:28 ` Stephan Mueller
2018-01-16 10:51 ` Jonathan Cameron
2018-01-15 14:37 ` Jonathan Cameron
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=2165621.DHQGk8sIp3@positron.chronox.de \
--to=smueller@chronox.de \
--cc=harsh@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=jonathan.cameron@huawei.com \
--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).