From: Herbert Xu <herbert@gondor.apana.org.au>
To: Phil Sutter <phil.sutter@viprinet.com>
Cc: linux-crypto@vger.kernel.org, stable@kernel.org,
#@zimbra.vipri.net, 3.0+@zimbra.vipri.net
Subject: Re: [PATCH] crypto: mv_cesa - fix final callback not ignoring input data
Date: Tue, 28 Feb 2012 19:30:04 +1100 [thread overview]
Message-ID: <20120228083004.GA31292@gondor.apana.org.au> (raw)
In-Reply-To: <1330341424-27438-1-git-send-email-phil.sutter@viprinet.com>
On Mon, Feb 27, 2012 at 12:17:04PM +0100, Phil Sutter wrote:
> Broken by commit 6ef84509f3d439ed2d43ea40080643efec37f54f for users
> passing a request with non-zero 'nbytes' field, like e.g. testmgr.
>
> Cc: <stable@kernel.org> # 3.0+
> Signed-off-by: Phil Sutter <phil.sutter@viprinet.com>
Patch applied. Thanks a lot!
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2012-02-28 8:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 13:03 mv_cesa hash functions Frank
2012-02-22 20:10 ` Nikos Mavrogiannopoulos
2012-02-23 14:17 ` Sebastian Andrzej Siewior
2012-02-23 18:34 ` Phil Sutter
2012-02-23 18:34 ` Phil Sutter
2012-02-25 7:38 ` Herbert Xu
2012-02-27 11:17 ` [PATCH] crypto: mv_cesa - fix final callback not ignoring input data Phil Sutter
2012-02-28 8:30 ` Herbert Xu [this message]
2012-05-05 22:49 ` mv_cesa dcache problem since 2.6.37 was: Re: mv_cesa hash functions Simon Baatz
2012-05-05 22:49 ` Simon Baatz
2012-05-06 12:25 ` Russell King - ARM Linux
2012-05-06 12:25 ` Russell King - ARM Linux
2012-05-07 16:50 ` Phil Sutter
2012-05-07 16:50 ` Phil Sutter
2012-05-08 20:50 ` Simon Baatz
2012-05-08 20:50 ` Simon Baatz
2012-05-07 13:01 ` Frank
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=20120228083004.GA31292@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=#@zimbra.vipri.net \
--cc=3.0+@zimbra.vipri.net \
--cc=linux-crypto@vger.kernel.org \
--cc=phil.sutter@viprinet.com \
--cc=stable@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 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.