[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180109074133.GA10094@gondor.apana.org.au>
Date: Tue, 9 Jan 2018 18:41:33 +1100
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Kamil Konieczny <k.konieczny@...tner.samsung.com>
Cc: "Tobin C. Harding" <me@...in.cc>,
"David S. Miller" <davem@...emloft.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
linux-kernel@...r.kernel.org,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>
Subject: Re: [PATCH] crypto: clear htmldocs build warnings for crypto/hash
On Mon, Jan 08, 2018 at 05:43:18PM +0100, Kamil Konieczny wrote:
> Is it mandatory for both async hash and shash ?
>
> in crypto/ahash.c in function
>
> static int crypto_ahash_init_tfm(struct crypto_tfm *tfm)
>
> there is:
>
> hash->export = ahash_no_export;
> hash->import = ahash_no_import;
>
> and later in the same function:
>
> if (alg->export)
> hash->export = alg->export;
> if (alg->import)
> hash->import = alg->import;
That's just a leftover from the old days before we started requiring
them. These should be removed so that the registration fails if
they're not provided.
The requirement has been in place for a while now and we have been
failing any algorithms with a zero statesize which is only used by
import/export.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists