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: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeff Layton <jlayton@redhat.com>
Subject: [GIT PULL] Additional NFSD changes for 6.1
Date: Sat, 8 Oct 2022 15:08:01 +0000	[thread overview]
Message-ID: <F578CDD7-B188-4A5A-A2BC-20FA40759862@oracle.com> (raw)

Hi Linus-

Here are two patches that prepare the way for addressing

  https://bugzilla.linux-nfs.org/show_bug.cgi?id=394


----- Pull request follows ----

The following changes since commit 895ddf5ed4c54ea9e3533606d7a8b4e4f27f95ef:

  nfsd: extra checks when freeing delegation stateids (2022-09-26 14:50:58 -0400)

are available in the Git repository at:

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

for you to fetch changes up to 243a5263014a30436c93ed3f1f864c1da845455e:

  nfsd: rework hashtable handling in nfsd_do_file_acquire (2022-10-05 10:57:48 -0400)

----------------------------------------------------------------
Follow-up:
- filecache code clean-ups

----------------------------------------------------------------
Jeff Layton (2):
      nfsd: fix nfsd_file_unhash_and_dispose
      nfsd: rework hashtable handling in nfsd_do_file_acquire

 fs/nfsd/filecache.c | 88 +++++++++++++++++++++++++++++-----------------------------------------------------------
 1 file changed, 29 insertions(+), 59 deletions(-)

--
Chuck Lever




             reply	other threads:[~2022-10-08 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 15:08 Chuck Lever III [this message]
2022-10-11  3:43 ` 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=F578CDD7-B188-4A5A-A2BC-20FA40759862@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=jlayton@redhat.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®