mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] lib: Move SipHash into lib/crypto/
Date: Tue, 6 Oct 2026 14:25:15 +0200	[thread overview]
Message-ID: <20261006122515.GA3185@quark> (raw)
In-Reply-To: <20261003162827.155527-1-ebiggers@kernel.org>

On Sat, Oct 03, 2026 at 06:28:27PM +0200, Eric Biggers wrote:
> The addition of SipHash to lib/ predated the existence of the
> lib/crypto/ directory.  Since SipHash is a cryptographic algorithm, move
> it from the top-level lib/ directory to lib/crypto/.
> 
> (This does mean HalfSipHash comes with it too, as it's in the same
> files.  But lib/crypto/ still seems like the proper place for both.)
> 
> Specifically:
> 
> - Move both siphash.c and siphash_kunit.c.  Keep the header
>   <linux/siphash.h> as-is for now.
> 
> - Drop the dedicated MAINTAINERS entry for SipHash, as per the
>   suggestion from Jason
>   (https://lore.kernel.org/r/asB7QVFMlgKgbje2@zx2c4.com/).  The C files
>   now just fold up to the "CRYPTO LIBRARY" entry.  Add the header
>   explicitly, as it otherwise would be left unmaintained.
> 
> - Move the kconfig option that controls the KUnit test.  Put
>   "CRYPTO_LIB" in its name and update the prompt and help text to make
>   it consistent with the other crypto library test options.
> 
> - Enable the KUnit test in lib/crypto/.kunitconfig.
> 
> - Link to siphash.rst from the appropriate place in libcrypto-hash.rst.
> 
> - Use obj-y instead of lib-y, for consistency with the fact that
>   currently lib/crypto/ doesn't use kbuild's support for library file
>   goals.  We could keep it as lib-y, but virtually every kernel needs
>   SipHash support anyway (with vsprintf, printk, IPv4, IPv6, etc.
>   depending on it) so there is no practical difference in this case.
> 
> Acked-by: Ard Biesheuvel <ardb@kernel.org>
> Acked-by: Jason A. Donenfeld <Jason@zx2c4.com>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> 
> This patch is targeting libcrypto-next

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next

- Eric

      reply	other threads:[~2026-10-06 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 16:28 Eric Biggers
2026-10-06 12:25 ` Eric Biggers [this message]

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=20261006122515.GA3185@quark \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --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®