From: Chuck Lever <chuck.lever@oracle.com>
To: stable@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: [GIT PULL] NFSD fixes for v6.1.y
Date: Tue, 20 Feb 2024 09:50:53 -0500 [thread overview]
Message-ID: <ZdS8TXWl3QKf0qdk@manet.1015granger.net> (raw)
The following changes since commit 8b4118fabd6eb75fed19483b04dab3a036886489:
Linux 6.1.78 (2024-02-16 19:06:32 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git nfsd-6.1.y
for you to fetch changes up to d432d1006b60bd6b5c38974727bdce78f449eeea:
nfsd: don't take fi_lock in nfsd_break_deleg_cb() (2024-02-16 13:58:29 -0500)
----------------------------------------------------------------
NeilBrown (2):
nfsd: fix RELEASE_LOCKOWNER
nfsd: don't take fi_lock in nfsd_break_deleg_cb()
fs/nfsd/nfs4state.c | 37 ++++++++++++++++++++-----------------
1 file changed, 20 insertions(+), 17 deletions(-)
--
Chuck Lever
next reply other threads:[~2024-02-20 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 14:50 Chuck Lever [this message]
2024-02-20 14:57 ` [GIT PULL] NFSD fixes for v6.1.y Greg KH
2024-02-20 14:59 ` Chuck Lever III
2024-02-20 15:19 ` Greg KH
2024-02-20 15:01 ` Greg KH
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=ZdS8TXWl3QKf0qdk@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.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