From: Benjamin Coddington <bcodding@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Fixup gss_status tracepoint error output
Date: Thu, 11 Jul 2024 11:48:56 -0400 [thread overview]
Message-ID: <C3887ED2-B331-4AC9-A73B-326D7DDAC5FD@redhat.com> (raw)
In-Reply-To: <Zo/6G7ANcWEWkd0l@tissot.1015granger.net>
On 11 Jul 2024, at 11:28, Chuck Lever wrote:
> On Thu, Jul 11, 2024 at 11:24:01AM -0400, Benjamin Coddington wrote:
>> The GSS routine errors are values, not flags.
>
> My reading of kernel and user space GSS code is that these are
> indeed flags and can be combined. The definitions are found in
> include/linux/sunrpc/gss_err.h:
>
> To wit:
>
> 116 /*
> 117 * Routine errors:
> 118 */
> 119 #define GSS_S_BAD_MECH (((OM_uint32) 1ul) << GSS_C_ROUTINE_ERROR_OFFSET)
> 120 #define GSS_S_BAD_NAME (((OM_uint32) 2ul) << GSS_C_ROUTINE_ERROR_OFFSET)
I read this as just values shifted left by a constant.
No where in-kernel are they bitwise combined. I noticed this problem in practice
while reading the tracepoint output from corrupted GSS hash routines.
Ben
next prev parent reply other threads:[~2024-07-11 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 15:24 [PATCH] SUNRPC: Fixup gss_status tracepoint error output Benjamin Coddington
2024-07-11 15:28 ` Chuck Lever
2024-07-11 15:43 ` Chuck Lever III
2024-07-11 15:48 ` Benjamin Coddington [this message]
2024-07-11 15:52 ` Chuck Lever III
2024-07-11 16:00 ` Benjamin Coddington
2024-07-11 17:14 ` Chuck Lever III
2024-07-12 11:35 ` Jeff Layton
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=C3887ED2-B331-4AC9-A73B-326D7DDAC5FD@redhat.com \
--to=bcodding@redhat.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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