From: Jan Glauber <jglauber@marvell.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Mahipal Challa <mahipalreddy2006@gmail.com>
Subject: Re: [PATCH] crypto: cavium/zip - fix collision with generic cra_driver_name
Date: Tue, 26 Feb 2019 07:55:54 +0000 [thread overview]
Message-ID: <20190226075545.GB15176@hc> (raw)
In-Reply-To: <20190223082323.4126-1-ebiggers@kernel.org>
On Sat, Feb 23, 2019 at 12:23:23AM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> The cavium/zip implementation of the deflate compression algorithm is
> incorrectly being registered under the generic driver name, which
> prevents the generic implementation from being registered with the
> crypto API when CONFIG_CRYPTO_DEV_CAVIUM_ZIP=y. Similarly the lzs
> algorithm (which does not currently have a generic implementation...)
> is incorrectly being registered as lzs-generic.
>
> Fix the naming collision by adding a suffix "-cavium" to the
> cra_driver_name of the cavium/zip algorithms.
The patch is fine, basically the same as:
https://marc.info/?l=linux-crypto-vger&m=152968599829763&w=2
Shouldn't we also rename deflate to deflate generic?
--Jan
> Fixes: 640035a2dc55 ("crypto: zip - Add ThunderX ZIP driver core")
> Cc: Mahipal Challa <mahipalreddy2006@gmail.com>
> Cc: Jan Glauber <jglauber@cavium.com>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> drivers/crypto/cavium/zip/zip_main.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/cavium/zip/zip_main.c b/drivers/crypto/cavium/zip/zip_main.c
> index e6b09e784e666..a8447a3cf3665 100644
> --- a/drivers/crypto/cavium/zip/zip_main.c
> +++ b/drivers/crypto/cavium/zip/zip_main.c
> @@ -351,6 +351,7 @@ static struct pci_driver zip_driver = {
>
> static struct crypto_alg zip_comp_deflate = {
> .cra_name = "deflate",
> + .cra_driver_name = "deflate-cavium",
> .cra_flags = CRYPTO_ALG_TYPE_COMPRESS,
> .cra_ctxsize = sizeof(struct zip_kernel_ctx),
> .cra_priority = 300,
> @@ -365,6 +366,7 @@ static struct crypto_alg zip_comp_deflate = {
>
> static struct crypto_alg zip_comp_lzs = {
> .cra_name = "lzs",
> + .cra_driver_name = "lzs-cavium",
> .cra_flags = CRYPTO_ALG_TYPE_COMPRESS,
> .cra_ctxsize = sizeof(struct zip_kernel_ctx),
> .cra_priority = 300,
> @@ -384,7 +386,7 @@ static struct scomp_alg zip_scomp_deflate = {
> .decompress = zip_scomp_decompress,
> .base = {
> .cra_name = "deflate",
> - .cra_driver_name = "deflate-scomp",
> + .cra_driver_name = "deflate-scomp-cavium",
> .cra_module = THIS_MODULE,
> .cra_priority = 300,
> }
> @@ -397,7 +399,7 @@ static struct scomp_alg zip_scomp_lzs = {
> .decompress = zip_scomp_decompress,
> .base = {
> .cra_name = "lzs",
> - .cra_driver_name = "lzs-scomp",
> + .cra_driver_name = "lzs-scomp-cavium",
> .cra_module = THIS_MODULE,
> .cra_priority = 300,
> }
> --
> 2.20.1
next prev parent reply other threads:[~2019-02-26 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 8:23 [PATCH] crypto: cavium/zip - fix collision with generic cra_driver_name Eric Biggers
2019-02-26 7:55 ` Jan Glauber [this message]
2019-02-26 22:28 ` Eric Biggers
2019-02-28 6:39 ` Herbert Xu
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=20190226075545.GB15176@hc \
--to=jglauber@marvell.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=mahipalreddy2006@gmail.com \
/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).