From: Chuck Lever <cel@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Trond Myklebust <trondmy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [GIT PULL] NFSD changes for v6.18
Date: Mon, 13 Oct 2025 15:37:02 -0400 [thread overview]
Message-ID: <f3a3f734-e75a-4d93-9a89-988417d5008c@kernel.org> (raw)
In-Reply-To: <20251013192103.GA61714@google.com>
On 10/13/25 3:21 PM, Eric Biggers wrote:
> On Mon, Oct 13, 2025 at 12:15:52PM +0200, Geert Uytterhoeven wrote:
>> Hi Chuck, Eric,
>>
>> On Wed, 8 Oct 2025 at 00:05, Chuck Lever <cel@kernel.org> wrote:
>>> Eric Biggers (4):
>>> SUNRPC: Make RPCSEC_GSS_KRB5 select CRYPTO instead of depending on it
>>
>> This is now commit d8e97cc476e33037 ("SUNRPC: Make RPCSEC_GSS_KRB5
>> select CRYPTO instead of depending on it") in v6.18-rc1.
>> As RPCSEC_GSS_KRB5 defaults to "y", CRYPTO is now auto-enabled in
>> defconfigs that didn't enable it before.
>>
>> Gr{oetje,eeting}s,
>>
>
> Now the config is:
>
> config RPCSEC_GSS_KRB5
> tristate "Secure RPC: Kerberos V mechanism"
> depends on SUNRPC
> default y
> select SUNRPC_GSS
> select CRYPTO
> select CRYPTO_SKCIPHER
> select CRYPTO_HASH
>
> Perhaps the 'default y' should be removed?
>
> Chuck, do you know why it's there?
The "default y" was added by 2010 commit df486a25900f ("NFS: Fix the
selection of security flavours in Kconfig"), then modified again by
commit e3b2854faabd ("SUNRPC: Fix the SUNRPC Kerberos V RPCSEC_GSS
module dependencies") in 2011.
Copying Trond, the author of both of those patches.
--
Chuck Lever
next prev parent reply other threads:[~2025-10-13 19:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:50 [GIT PULL] NFSD changes for v6.18 Chuck Lever
2025-10-06 20:51 ` Linus Torvalds
2025-10-06 20:58 ` Chuck Lever
2025-10-07 11:26 ` Christian Brauner
2025-10-07 11:47 ` Jeff Layton
2025-10-07 12:06 ` Christian Brauner
2025-10-06 21:20 ` Johannes Berg
2025-10-06 21:54 ` Linus Torvalds
2025-10-06 21:00 ` pr-tracker-bot
2025-10-13 10:15 ` Geert Uytterhoeven
2025-10-13 19:21 ` Eric Biggers
2025-10-13 19:37 ` Chuck Lever [this message]
2025-10-16 14:31 ` Jeff Layton
2025-10-16 14:36 ` Geert Uytterhoeven
2025-10-16 15:04 ` Chuck Lever
2025-10-16 15:19 ` Trond Myklebust
2025-10-16 18:02 ` Eric Biggers
2025-10-16 18:09 ` Chuck Lever
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=f3a3f734-e75a-4d93-9a89-988417d5008c@kernel.org \
--to=cel@kernel.org \
--cc=ebiggers@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@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