From: Scott Mayhew <smayhew@redhat.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
trondmy@kernel.org, anna@kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Check if we need to recalculate slack estimates
Date: Fri, 13 Feb 2026 17:45:15 -0500 [thread overview]
Message-ID: <aY-pe7-FhRpPy5J2@aion> (raw)
In-Reply-To: <aVe7TOFVxckWdF1m@eldamar.lan>
On Fri, 02 Jan 2026, Salvatore Bonaccorso wrote:
> Hi Chuck, Scott,
>
> On Wed, Nov 19, 2025 at 10:48:47AM -0500, Chuck Lever wrote:
> > On 11/19/25 8:32 AM, Scott Mayhew wrote:
> > > If the incoming GSS verifier is larger than what we previously recorded
> > > on the gss_auth, that would indicate the GSS cred/context used for that
> > > RPC is using a different enctype than the one used by the machine
> > > cred/context, and we should recalculate the slack variables accordingly.
> > >
> > > Link: https://bugs.debian.org/1120598
> > > Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> > > ---
> > > net/sunrpc/auth_gss/auth_gss.c | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git a/net/sunrpc/auth_gss/auth_gss.c b/net/sunrpc/auth_gss/auth_gss.c
> > > index 5c095cb8cb20..6da9ca08370d 100644
> > > --- a/net/sunrpc/auth_gss/auth_gss.c
> > > +++ b/net/sunrpc/auth_gss/auth_gss.c
> > > @@ -1721,6 +1721,14 @@ gss_validate(struct rpc_task *task, struct xdr_stream *xdr)
> > > if (maj_stat)
> > > goto bad_mic;
> > >
> > > + /*
> > > + * Normally we only recalculate the slack variables once after
> > > + * creating a new gss_auth, but we should also do it if the incoming
> > > + * verifier has a larger size than what was previously recorded.
> >
> > No quibble with the code change, but IMO the comment should work a
> > little harder to explain why the increase is needed. Something like:
> >
> > * When the incoming verifier is larger than expected, the
> > * GSS context is using a different enctype than the one used
> > * initially by the machine credential. Force a slack size update
> > * to maintain good payload alignment.
> >
> > I'm summarizing based on your commit message above...
> >
> >
> > > + */
> > > + if (cred->cr_auth->au_verfsize < (XDR_QUADLEN(len) + 2))
> > > + __set_bit(RPCAUTH_AUTH_UPDATE_SLACK, &cred->cr_auth->au_flags);
> > > +
> > > /* We leave it to unwrap to calculate au_rslack. For now we just
> > > * calculate the length of the verifier: */
> > > if (test_bit(RPCAUTH_AUTH_UPDATE_SLACK, &cred->cr_auth->au_flags))
>
> I was looking in Debian for the state of this and noticed this was
> later on never applied/submitted to mainline, is this correct? Did it
> felt through the cracks or is it considered not to be a problem to
> further tackle?
>
> Thanks a lot for your work and your help!
Sorry for the delay. After having had a chance to take a deeper look,
I think it would be better to try to address this from the rpc.gssd side
instead of trying to make the kernel cope with having to bounce around
between different encryption types.
Unfortunately I fat-fingered your email address when I sent the patches,
so here's the link:
https://lore.kernel.org/linux-nfs/20260213224012.2608126-1-smayhew@redhat.com/T/#t
-Scott
>
> Regards,
> Salvatore
>
next prev parent reply other threads:[~2026-02-13 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 13:32 [PATCH] SUNRPC: Check if we need to recalculate slack estimates Scott Mayhew
2025-11-19 15:48 ` Chuck Lever
2026-01-02 12:34 ` Salvatore Bonaccorso
2026-01-02 14:49 ` Chuck Lever
2026-02-13 22:45 ` Scott Mayhew [this message]
2026-02-14 15:57 ` Salvatore Bonaccorso
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=aY-pe7-FhRpPy5J2@aion \
--to=smayhew@redhat.com \
--cc=anna@kernel.org \
--cc=carnil@debian.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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