From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] lib/crc-t10dif: remove digest and block size constants
Date: Thu, 6 Feb 2025 08:39:46 -0800 [thread overview]
Message-ID: <20250206163946.GB4283@sol.localdomain> (raw)
In-Reply-To: <CAMj1kXGjc6Abm1eHANt7w=D5eVpJXHHNo_7ZcyRMNMNwirZoHg@mail.gmail.com>
On Thu, Feb 06, 2025 at 12:09:22PM +0100, Ard Biesheuvel wrote:
> On Tue, 4 Feb 2025 at 21:11, Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > From: Eric Biggers <ebiggers@google.com>
> >
> > These constants are only used in crypto/crct10dif_generic.c, and they
> > are better off just hardcoded there.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> >
> > I'm planning to take this via the crc tree.
> >
>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
>
> Could you remind me why we are keeping this driver?
>
I don't know. I had to keep "crc32" and "crc32c" around for now because they
are still used, and I just defaulted to doing the same for "crct10dif". It
*looks like* "crct10dif" is different and we could indeed safely remove it like
I ended up doing for "crc64-rocksoft", though. "crct10dif" has no remaining
references in the kernel; it has no references in cryptsetup, iwd, or libell;
and Debian Code Search doesn't find anything else. It's over a decade old, so I
was worried there was time for users to have crept in, but that doesn't seem to
have happened. So yeah, good idea. I'll send a patch that removes it, with the
device-mapper folks Cc'd in case they know of anything else.
- Eric
next prev parent reply other threads:[~2025-02-06 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 20:11 Eric Biggers
2025-02-06 11:09 ` Ard Biesheuvel
2025-02-06 16:39 ` Eric Biggers [this message]
2025-02-06 16:57 ` Ard Biesheuvel
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=20250206163946.GB4283@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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 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®