[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <174845587080.200069.9203268802136145057.b4-ty@oracle.com>
Date: Wed, 28 May 2025 14:11:53 -0400
From: cel@...nel.org
To: Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Trond Myklebust <trondmy@...nel.org>,
Anna Schumaker <anna@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
NeilBrown <neil@...wn.name>,
Jeff Layton <jlayton@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
Mike Snitzer <snitzer@...nel.org>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] nfsd: use threads array as-is in netlink thread set interface
From: Chuck Lever <chuck.lever@...cle.com>
On Tue, 27 May 2025 20:12:46 -0400, Jeff Layton wrote:
> The first patch is probably appropriate for stable. It should fix
> problems when someone sets the pool_mode to pernode, without userland
> sending down a fully-populated thread array.
>
> The second patch just adds a couple of new tracepoints that I ended up
> using to track this down.
>
> [...]
Applied to nfsd-testing, thanks!
[1/2] nfsd: use threads array as-is in netlink interface
commit: b2a9a114a3c7f5abfa2875b70ce9b73525a74291
[2/2] sunrpc: new tracepoints around svc thread wakeups
commit: 65b8babe551bddf00aac69bc905f88a4e0371766
--
Chuck Lever
Powered by blists - more mailing lists