From: Eric Biggers <ebiggers@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chuck Lever <cel@kernel.org>,
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 19:21:03 +0000 [thread overview]
Message-ID: <20251013192103.GA61714@google.com> (raw)
In-Reply-To: <CAMuHMdVYNUBH11trBr2Mo3i_fDh5sw5AzqYbPwO7_m4H6Y3sfA@mail.gmail.com>
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?
- Eric
next prev parent reply other threads:[~2025-10-13 19:21 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 [this message]
2025-10-13 19:37 ` Chuck Lever
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=20251013192103.GA61714@google.com \
--to=ebiggers@kernel.org \
--cc=cel@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 \
/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