From: Herbert Xu <herbert@gondor.apana.org.au>
To: dsterba@suse.cz, Nikolay Borisov <nborisov@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/2] libcrc32c: Add crc32c_impl function
Date: Sat, 3 Feb 2018 17:51:37 +0800 [thread overview]
Message-ID: <20180203095137.GD28936@gondor.apana.org.au> (raw)
In-Reply-To: <20180202172942.GU18553@twin.jikos.cz>
On Fri, Feb 02, 2018 at 06:29:42PM +0100, David Sterba wrote:
> Adding linux-crypto@vger.kernel.org to CC
>
> Link to the 2/2 patch https://patchwork.kernel.org/patch/10149203/
>
> On Mon, Jan 08, 2018 at 11:45:04AM +0200, Nikolay Borisov wrote:
> > This function returns a string with the currently in-use implementation
> > of the crc32c algorithm, i.e crc32c-generic (for unoptimised, generic
> > implementation) or crc32c-intel for the sse optimised version. This
> > will be used by btrfs.
> >
> > Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> > ---
> > include/linux/crc32c.h | 1 +
> > lib/libcrc32c.c | 6 ++++++
> > 2 files changed, 7 insertions(+)
> >
> > diff --git a/include/linux/crc32c.h b/include/linux/crc32c.h
> > index 357ae4611a45..bd21af828ff6 100644
> > --- a/include/linux/crc32c.h
> > +++ b/include/linux/crc32c.h
> > @@ -5,6 +5,7 @@
> > #include <linux/types.h>
> >
> > extern u32 crc32c(u32 crc, const void *address, unsigned int length);
> > +extern const char *crc32c_impl(void);
> >
> > /* This macro exists for backwards-compatibility. */
> > #define crc32c_le crc32c
> > diff --git a/lib/libcrc32c.c b/lib/libcrc32c.c
> > index 9f79547d1b97..eaf71e0e04be 100644
> > --- a/lib/libcrc32c.c
> > +++ b/lib/libcrc32c.c
> > @@ -71,6 +71,12 @@ static void __exit libcrc32c_mod_fini(void)
> > crypto_free_shash(tfm);
> > }
> >
> > +const char *crc32c_impl(void)
> > +{
> > + return crypto_tfm_alg_driver_name(crypto_shash_tfm(tfm));
> > +}
> > +EXPORT_SYMBOL(crc32c_impl);
You could just use crypto_shash_driver_name.
> Crypto maintainers, would it be still possible to squeeze this patch to
> 4.16? It's quite trivial, but as it is not in a code I maintain I'm not
> comfortable to add it to my tree (unless I get an ACK).
>
> The linked patch depends on that change and would let us get rid of some
> custom crypto wrappers around crc32c.
I'm fine with the patch otherwise.
Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
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:[~2018-02-03 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 9:45 [PATCH 0/2] Remove custom crc32c init code from btrfs Nikolay Borisov
2018-01-08 9:45 ` [PATCH 1/2] libcrc32c: Add crc32c_impl function Nikolay Borisov
2018-02-02 17:29 ` David Sterba
2018-02-03 9:51 ` Herbert Xu [this message]
2018-01-08 9:45 ` [PATCH 2/2] btrfs: Remove custom crc32c init code Nikolay Borisov
2018-02-02 17:17 ` David Sterba
2018-02-02 19:46 ` Andy Shevchenko
2018-02-05 22:53 ` David Sterba
2018-01-08 10:21 ` [PATCH 0/2] Remove custom crc32c init code from btrfs Timofey Titovets
2018-01-08 12:30 ` Nikolay Borisov
2018-02-05 22:59 ` David Sterba
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=20180203095137.GD28936@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.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
all inboxes | Powered by JetHome®