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 bugfixes for 5.18
Date: Fri, 13 May 2022 17:12:18 +0000 [thread overview]
Message-ID: <bfd5b2161954d919909450ab9737308e6299ee11.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 4b97bac0756a81cda5afd45417a99b5bccdcff67:
Merge tag 'for-5.18-rc5-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2022-05-06 14:32:16 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.18-4
for you to fetch changes up to 085d16d5f949b64713d5e960d6c9bbf51bc1d511:
nfs: fix broken handling of the softreval mount option (2022-05-09 13:02:54 -0400)
One more pull request. There was a bug in the fix to ensure that gss-
proxy continues to work correctly after we fixed the AF_LOCAL socket
leak in the RPC code. This request therefore reverts that broken patch,
and replaces it with one that works correctly.
Thanks,
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 5.18
Highlights include:
Stable fixes:
- SUNRPC: Ensure that the gssproxy client can start in a connected state
Bugfixes:
- Revert "SUNRPC: Ensure gss-proxy connects on setup"
- nfs: fix broken handling of the softreval mount option
----------------------------------------------------------------
Dan Aloni (1):
nfs: fix broken handling of the softreval mount option
Trond Myklebust (2):
Revert "SUNRPC: Ensure gss-proxy connects on setup"
SUNRPC: Ensure that the gssproxy client can start in a connected state
fs/nfs/fs_context.c | 2 +-
include/linux/sunrpc/clnt.h | 2 +-
net/sunrpc/auth_gss/gss_rpc_upcall.c | 3 ++-
net/sunrpc/clnt.c | 36 +++++++++++++++++++++++++++++++++---
4 files changed, 37 insertions(+), 6 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2022-05-13 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 17:12 Trond Myklebust [this message]
2022-05-13 18:57 ` 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=bfd5b2161954d919909450ab9737308e6299ee11.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
all inboxes | Powered by JetHome®