public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Mat Martineau <martineau@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Matthieu Baerts <matttbe@kernel.org>,
	netdev@vger.kernel.org,  mptcp@lists.linux.dev,
	Geliang Tang <geliang@kernel.org>
Subject: Re: [PATCH net] mptcp: select CRYPTO_LIB_UTILS instead of CRYPTO
Date: Fri, 5 Dec 2025 08:55:35 -0800 (PST)	[thread overview]
Message-ID: <4eaa66fd-cd4e-a5af-1d6b-6d8a95150d3f@kernel.org> (raw)
In-Reply-To: <20251204054417.491439-1-ebiggers@kernel.org>

On Wed, 3 Dec 2025, Eric Biggers wrote:

> Since the only crypto functions used by the mptcp code are the SHA-256
> library functions and crypto_memneq(), select only the options needed
> for those: CRYPTO_LIB_SHA256 and CRYPTO_LIB_UTILS.
>
> Previously, CRYPTO was selected instead of CRYPTO_LIB_UTILS.  That does
> pull in CRYPTO_LIB_UTILS as well, but it's unnecessarily broad.
>
> Years ago, the CRYPTO_LIB_* options were visible only when CRYPTO.  That
> may be another reason why CRYPTO is selected here.  However, that was
> fixed years ago, and the libraries can now be selected directly.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> net/mptcp/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)

Thanks Eric!

Yes, this is a case of our Kconfig predating CRYPTO_LIB_UTILS. Appreciate 
the fix.

Netdev maintainers, it's fine to apply this directly to the -net tree.

Reviewed-by: Mat Martineau <martineau@kernel.org>


>
> diff --git a/net/mptcp/Kconfig b/net/mptcp/Kconfig
> index 20328920f6ed..be71fc9b4638 100644
> --- a/net/mptcp/Kconfig
> +++ b/net/mptcp/Kconfig
> @@ -2,11 +2,11 @@
> config MPTCP
> 	bool "MPTCP: Multipath TCP"
> 	depends on INET
> 	select SKB_EXTENSIONS
> 	select CRYPTO_LIB_SHA256
> -	select CRYPTO
> +	select CRYPTO_LIB_UTILS
> 	help
> 	  Multipath TCP (MPTCP) connections send and receive data over multiple
> 	  subflows in order to utilize multiple network paths. Each subflow
> 	  uses the TCP protocol, and TCP options carry header information for
> 	  MPTCP.
>
> base-commit: b2c27842ba853508b0da00187a7508eb3a96c8f7
> -- 
> 2.52.0
>
>

  parent reply	other threads:[~2025-12-05 16:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  5:44 [PATCH net] mptcp: select CRYPTO_LIB_UTILS instead of CRYPTO Eric Biggers
2025-12-05 15:06 ` MPTCP CI
2025-12-05 16:55 ` Mat Martineau [this message]
2025-12-09 11:50 ` patchwork-bot+netdevbpf

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=4eaa66fd-cd4e-a5af-1d6b-6d8a95150d3f@kernel.org \
    --to=martineau@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=geliang@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@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