<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/trace/events/rpcgss.h, branch linux-6.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.2.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.2.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-12-10T16:01:12Z</updated>
<entry>
<title>trace: Relocate event helper files</title>
<updated>2022-12-10T16:01:12Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2022-11-14T13:57:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=247c01ff5f8d66e62a404c91733be52fecb8b7f6'/>
<id>urn:sha1:247c01ff5f8d66e62a404c91733be52fecb8b7f6</id>
<content type='text'>
Steven Rostedt says:
&gt; The include/trace/events/ directory should only hold files that
&gt; are to create events, not headers that hold helper functions.
&gt;
&gt; Can you please move them out of include/trace/events/ as that
&gt; directory is "special" in the creation of events.

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Acked-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;
Acked-by: Steven Rostedt (Google) &lt;rostedt@goodmis.org&gt;
Acked-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>sunrpc: fix header include guard in trace header</title>
<updated>2021-11-17T23:27:32Z</updated>
<author>
<name>Thiago Rafael Becker</name>
</author>
<published>2021-11-17T13:26:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=268bb03856ed6c8511c31d08de0148782f50822f'/>
<id>urn:sha1:268bb03856ed6c8511c31d08de0148782f50822f</id>
<content type='text'>
rpcgss.h include protection was protecting against the define for
rpcrdma.h.

Signed-off-by: Thiago Rafael Becker &lt;trbecker@gmail.com&gt;
Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Tracepoints should display tk_pid and cl_clid as a fixed-size field</title>
<updated>2021-10-20T22:09:54Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2021-10-16T22:02:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b4776a341ec05e809d21e98db5ed49dbdc81d5d8'/>
<id>urn:sha1:b4776a341ec05e809d21e98db5ed49dbdc81d5d8</id>
<content type='text'>
For certain special cases, RPC-related tracepoints record a -1 as
the task ID or the client ID. It's ugly for a trace event to display
4 billion in these cases.

To help keep SUNRPC tracepoints consistent, create a macro that
defines the print format specifiers for tk_pid and cl_clid. At some
point in the future we might try tk_pid with a wider range of values
than 0..64K so this makes it easier to make that change.

RPC tracepoints now look like this:

&lt;...&gt;-1276  [009]   149.720358: rpc_clnt_new:         client=00000005 peer=[192.168.2.55]:20049 program=nfs server=klimt.ib

&lt;...&gt;-1342  [004]   149.921234: rpc_xdr_recvfrom:     task:0000001a@00000005 head=[0xff1242d9ab6dc01c,144] page=0 tail=[(nil),0] len=144
&lt;...&gt;-1342  [004]   149.921235: xprt_release_cong:    task:0000001a@00000005 snd_task:ffffffff cong=256 cwnd=16384
&lt;...&gt;-1342  [004]   149.921235: xprt_put_cong:        task:0000001a@00000005 snd_task:ffffffff cong=0 cwnd=16384

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Signed-off-by: Trond Myklebust &lt;trond.myklebust@hammerspace.com&gt;
</content>
</entry>
<entry>
<title>treewide: Add missing semicolons to __assign_str uses</title>
<updated>2021-06-30T13:19:14Z</updated>
<author>
<name>Joe Perches</name>
</author>
<published>2021-06-12T15:42:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=78c14b385c195d4f25ab7c19186b8897a5b9ae3f'/>
<id>urn:sha1:78c14b385c195d4f25ab7c19186b8897a5b9ae3f</id>
<content type='text'>
The __assign_str macro has an unusual ending semicolon but the vast
majority of uses of the macro already have semicolon termination.

$ git grep -P '\b__assign_str\b' | wc -l
551
$ git grep -P '\b__assign_str\b.*;' | wc -l
480

Add semicolons to the __assign_str() uses without semicolon termination
and all the other uses without semicolon termination via additional defines
that are equivalent to __assign_str() with the eventual goal of removing
the semicolon from the __assign_str() macro definition.

Link: https://lore.kernel.org/lkml/1e068d21106bb6db05b735b4916bb420e6c9842a.camel@perches.com/
Link: https://lkml.kernel.org/r/48a056adabd8f70444475352f617914cef504a45.camel@perches.com

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Augment server-side rpcgss tracepoints</title>
<updated>2020-07-13T21:28:24Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2020-04-18T22:30:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=10b9d99a3dbbf5e9af838d1887a1047875dcafd9'/>
<id>urn:sha1:10b9d99a3dbbf5e9af838d1887a1047875dcafd9</id>
<content type='text'>
Add similar tracepoints to those that were recently added on the
client side to track failures in the integ and priv unwrap paths.

And, let's collect the seqno-specific tracepoints together with a
common naming convention.

Regarding the gss_check_seq_num() changes: everywhere else treats
the GSS sequence number as an unsigned 32-bit integer. As far back
as 2.6.12, I couldn't find a compelling reason to do things
differently here. As a defensive change it's better to eliminate
needless implicit sign conversions.

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Trace GSS context lifetimes</title>
<updated>2020-06-11T17:33:47Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2020-05-12T21:13:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74fb8fecee99f61415dcb6e22dbc24f42988a1d3'/>
<id>urn:sha1:74fb8fecee99f61415dcb6e22dbc24f42988a1d3</id>
<content type='text'>
Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: receive buffer size estimation values almost never change</title>
<updated>2020-06-11T17:33:47Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2020-05-12T21:13:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=53bc19f17f21738735706fabcae3070f16c833db'/>
<id>urn:sha1:53bc19f17f21738735706fabcae3070f16c833db</id>
<content type='text'>
Avoid unnecessary cache sloshing by placing the buffer size
estimation update logic behind an atomic bit flag.

The size of GSS information included in each wrapped Reply does
not change during the lifetime of a GSS context. Therefore, the
au_rslack and au_ralign fields need to be updated only once after
establishing a fresh GSS credential.

Thus a slack size update must occur after a cred is created,
duplicated, renewed, or expires. I'm not sure I have this exactly
right. A trace point is introduced to track updates to these
variables to enable troubleshooting the problem if I missed a spot.

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Clean up: Replace dprintk and BUG_ON call sites in svcauth_gss.c</title>
<updated>2020-03-16T16:04:31Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2020-03-02T20:16:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=28155524eaa2eabdc97e588db195d0a45d7e4d6f'/>
<id>urn:sha1:28155524eaa2eabdc97e588db195d0a45d7e4d6f</id>
<content type='text'>
Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Trace gssproxy upcall results</title>
<updated>2019-10-30T20:32:07Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2019-10-24T13:34:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ff27e9f748303e8567bfceb6d7ff264cbcaca2ef'/>
<id>urn:sha1:ff27e9f748303e8567bfceb6d7ff264cbcaca2ef</id>
<content type='text'>
Record results of a GSS proxy ACCEPT_SEC_CONTEXT upcall and the
svc_authenticate() function to make field debugging of NFS server
Kerberos issues easier.

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Reviewed-by: Bill Baker &lt;bill.baker@oracle.com&gt;
Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Introduce trace points in rpc_auth_gss.ko</title>
<updated>2019-02-14T14:20:40Z</updated>
<author>
<name>Chuck Lever</name>
</author>
<published>2019-02-11T16:25:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0c77668ddb4e7bdfbca462c6185d154d0b8889ae'/>
<id>urn:sha1:0c77668ddb4e7bdfbca462c6185d154d0b8889ae</id>
<content type='text'>
Add infrastructure for trace points in the RPC_AUTH_GSS kernel
module, and add a few sample trace points. These report exceptional
or unexpected events, and observe the assignment of GSS sequence
numbers.

Signed-off-by: Chuck Lever &lt;chuck.lever@oracle.com&gt;
Signed-off-by: Anna Schumaker &lt;Anna.Schumaker@Netapp.com&gt;
</content>
</entry>
</feed>
