From: Tadeusz Struk <tadeusz.struk@intel.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, stable@vger.kernel.org,
tadeusz.struk@intel.com
Subject: [PATCH 0/3] crypto: afalg_skcipher - fixes after skcipher conversion
Date: Wed, 27 Jan 2016 09:13:50 -0800 [thread overview]
Message-ID: <20160127171350.32579.49931.stgit@tstruk-mobl1> (raw)
Hi Herbert,
While testing the algif_aead async patch, I have rerun the async
algif_skcipher tests and I have found some problems.
There are three different issues around algif_skcipher and skcipher.
Two are skcipher conversion related, and one is a bug in the
algif_skcipher, not related to the conversion. It started to
manifest itself after a fix the the qat driver.
---
Tadeusz Struk (3):
crypto: skcipher - return the correct request to the user
crypto: algif_skcipher - fix async callback after skcipher convertion
crypto: algif_skcipher - fix increase private contex space for async request
crypto/algif_skcipher.c | 11 +++++++----
crypto/skcipher.c | 11 ++++++++++-
2 files changed, 17 insertions(+), 5 deletions(-)
--
next reply other threads:[~2016-01-27 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 17:13 Tadeusz Struk [this message]
2016-01-27 17:13 ` [PATCH 1/3] crypto: skcipher - return the correct request to the user Tadeusz Struk
2016-01-28 4:53 ` Herbert Xu
2016-01-27 17:14 ` [PATCH 2/3] crypto: algif_skcipher - fix async callback after skcipher convertion Tadeusz Struk
2016-01-28 4:56 ` Herbert Xu
2016-01-27 17:14 ` [PATCH 3/3] crypto: algif_skcipher - increase private contex space for async request Tadeusz Struk
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=20160127171350.32579.49931.stgit@tstruk-mobl1 \
--to=tadeusz.struk@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@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