From: Herbert Xu <herbert@gondor.apana.org.au>
To: Frank <frank@debian-nas.org>,
'Sebastian Andrzej Siewior' <sebastian@breakpoint.cc>,
uri@jdland.co.il, linux-crypto@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
Simon Baatz <simon2012@baatz.info>
Subject: Re: mv_cesa hash functions
Date: Sat, 25 Feb 2012 18:38:12 +1100 [thread overview]
Message-ID: <20120225073806.GA19079@gondor.apana.org.au> (raw)
In-Reply-To: <20120223183439.GA18545@orbit.nwl.cc>
On Thu, Feb 23, 2012 at 07:34:39PM +0100, Phil Sutter wrote:
>
> Herbert, please clarify: is it intended behaviour that ahash_alg's final
> callback ignores possibly present data in the request? If I wanted to
> finalise a hash operation with some final data, would I then use the
> finup callback instead? (Note the implied question of the actual
> difference between the two callbacks.)
final should ignore any data present in the request. So we should
fix this up in mv_cesa.
Cheers,
--
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-25 8:09 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 [this message]
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
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=20120225073806.GA19079@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=catalin.marinas@arm.com \
--cc=frank@debian-nas.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-crypto@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
--cc=simon2012@baatz.info \
--cc=uri@jdland.co.il \
/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.