From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client fixes for 5.18
Date: Fri, 6 May 2022 20:09:29 +0000 [thread overview]
Message-ID: <cdd6481d128894041e6251218a309ae9cfa15f0b.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit b2d229d4ddb17db541098b83524d901257e93845:
Linux 5.18-rc3 (2022-04-17 13:57:31 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.18-3
for you to fetch changes up to a3d0562d4dc039bca39445e1cddde7951662e17d:
Revert "SUNRPC: attempt AF_LOCAL connect on setup" (2022-04-29 20:38:27 -0400)
Cheers,
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 5.18
Highlights include:
Stable fixes:
- Fix a socket leak when setting up an AF_LOCAL RPC client
- Ensure that knfsd connects to the gss-proxy daemon on setup
Bugfixes:
- Fix a refcount leak when migrating a task off an offlined transport
- Don't gratuitously invalidate inode attributes on delegation return
- Don't leak sockets in xs_local_connect()
- Ensure timely close of disconnected AF_LOCAL sockets
----------------------------------------------------------------
Olga Kornievskaia (1):
SUNRPC release the transport of a relocated task with an assigned transport
Trond Myklebust (5):
NFSv4: Don't invalidate inode attributes on delegation return
SUNRPC: Don't leak sockets in xs_local_connect()
SUNRPC: Ensure timely close of disconnected AF_LOCAL sockets
SUNRPC: Ensure gss-proxy connects on setup
Revert "SUNRPC: attempt AF_LOCAL connect on setup"
fs/nfs/nfs4proc.c | 12 +++++++++++-
include/linux/sunrpc/clnt.h | 1 +
net/sunrpc/auth_gss/gss_rpc_upcall.c | 2 +-
net/sunrpc/clnt.c | 14 ++++++++++----
net/sunrpc/xprtsock.c | 35 +++++++++++++++++++++++++++++++----
5 files changed, 54 insertions(+), 10 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2022-05-06 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 20:09 Trond Myklebust [this message]
2022-05-06 20:29 ` [GIT PULL] Please pull NFS client fixes for 5.18 pr-tracker-bot
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=cdd6481d128894041e6251218a309ae9cfa15f0b.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--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;
as well as URLs for NNTP newsgroup(s).