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@kernel.org>
Subject: [GIT PULL] second v6.2-rc pull request for nfsd
Date: Tue, 10 Jan 2023 19:13:21 +0000 [thread overview]
Message-ID: <C9754BD7-5CC7-4330-9A1B-F6C67EB2CB3F@oracle.com> (raw)
The following changes since commit cad853374d85fe678d721512cecfabd7636e51f3:
nfsd: fix handling of readdir in v4root vs. mount upcall timeout (2023-01-02 10:45:31 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.2-3
for you to fetch changes up to 5304930dbae82d259bcf7e5611db7c81e7a42eff:
NFSD: Use set_bit(RQ_DROPME) (2023-01-07 10:16:33 -0500)
----------------------------------------------------------------
nfsd-6.2 fixes:
- Fix a race when creating NFSv4 files
- Revert the use of relaxed bitops
----------------------------------------------------------------
Chuck Lever (2):
Revert "SUNRPC: Use RMW bitops in single-threaded hot paths"
NFSD: Use set_bit(RQ_DROPME)
Jeff Layton (1):
nfsd: fix handling of cached open files in nfsd4_open codepath
fs/nfsd/filecache.c | 40 ++++++++++++++++++++++------------------
fs/nfsd/filecache.h | 5 +++--
fs/nfsd/nfs4proc.c | 7 +++----
fs/nfsd/nfs4state.c | 16 ++++------------
fs/nfsd/nfs4xdr.c | 2 +-
fs/nfsd/nfsproc.c | 4 ++--
fs/nfsd/trace.h | 52 +++++++++++++---------------------------------------
net/sunrpc/auth_gss/svcauth_gss.c | 4 ++--
net/sunrpc/svc.c | 6 +++---
net/sunrpc/svc_xprt.c | 2 +-
net/sunrpc/svcsock.c | 8 ++++----
net/sunrpc/xprtrdma/svc_rdma_transport.c | 2 +-
12 files changed, 59 insertions(+), 89 deletions(-)
--
Chuck Lever
next reply other threads:[~2023-01-10 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 19:13 Chuck Lever III [this message]
2023-01-10 21:06 ` [GIT PULL] second v6.2-rc pull request for nfsd 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=C9754BD7-5CC7-4330-9A1B-F6C67EB2CB3F@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jlayton@kernel.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