mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bruce Fields <bfields@fieldses.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] nfsd changes for 5.17-rc
Date: Wed, 2 Feb 2022 16:32:22 +0000	[thread overview]
Message-ID: <F1000CFA-4575-4BBA-8640-4BF09A3F0811@oracle.com> (raw)

Hi Linus -

The following changes since commit 16720861675393a35974532b3c837d9fd7bfe08c:

  SUNRPC: Fix sockaddr handling in svcsock_accept_class trace points (2022-01-10 10:57:34 -0500)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-5.17-1

for you to fetch changes up to ab451ea952fe9d7afefae55ddb28943a148247fe:

  nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. (2022-01-28 09:04:00 -0500)

----------------------------------------------------------------
Notable bug fixes:
- Ensure SM_NOTIFY doesn't crash the NFS server host
- Ensure NLM locks are cleaned up after client reboot
- Fix a leak of internal NFSv4 lease information

----------------------------------------------------------------
Dai Ngo (1):
      nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client.

J. Bruce Fields (2):
      lockd: fix server crash on reboot of client holding lock
      lockd: fix failure to cleanup client locks

 fs/lockd/svcsubs.c  | 18 ++++++++++--------
 fs/nfsd/nfs4state.c |  4 +++-
 2 files changed, 13 insertions(+), 9 deletions(-)

--
Chuck Lever




             reply	other threads:[~2022-02-02 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 16:32 Chuck Lever III [this message]
2022-02-02 18:19 ` 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=F1000CFA-4575-4BBA-8640-4BF09A3F0811@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=bfields@fieldses.org \
    --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®