From: Milan Broz <gmazyland@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dm-devel@lists.linux.dev,
Atharva Tiwari <evepolonium@gmail.com>,
Shane Wang <shane.wang@intel.com>
Subject: Re: [PATCH] crypto: vmac - remove unused VMAC algorithm
Date: Thu, 2 Jan 2025 09:49:45 +0100 [thread overview]
Message-ID: <86e3502f-5d24-4779-9d3b-3cd79288fa0d@gmail.com> (raw)
In-Reply-To: <20241226194309.27733-1-ebiggers@kernel.org>
On 12/26/24 8:43 PM, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Remove the vmac64 template, as it has no known users. It also continues
> to have longstanding bugs such as alignment violations (see
> https://lore.kernel.org/r/20241226134847.6690-1-evepolonium@gmail.com/).
...
> No in-tree user has appeared since then, other than potentially the
> usual components that allow specifying arbitrary hash algorithms by
> name, namely AF_ALG and dm-integrity. However there are no indications
> that VMAC is being used with these components. Debian Code Search and
> web searches for "vmac64" (the actual algorithm name) do not return any
> results other than the kernel itself, suggesting that it does not appear
> in any other code or documentation. Explicitly grepping the source code
> of the usual suspects (libell, iwd, cryptsetup) finds no matches either.
AFAIK it was never used for dm-integrity / cryptsetup and I am not even able
to make it work for test now (isn't the vmac64 alg module init even broken?).
Just remove it...
Thanks,
Milan
next prev parent reply other threads:[~2025-01-02 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 19:43 [PATCH] crypto: vmac - remove unused VMAC algorithm Eric Biggers
2024-12-27 8:43 ` Ard Biesheuvel
2024-12-30 11:05 ` Geert Uytterhoeven
2025-01-02 8:49 ` Milan Broz [this message]
2025-01-04 1:18 ` 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=86e3502f-5d24-4779-9d3b-3cd79288fa0d@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=evepolonium@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shane.wang@intel.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