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>
Subject: [GIT PULL] 1st set of changes for v5.18-rc
Date: Tue, 12 Apr 2022 22:21:16 +0000 [thread overview]
Message-ID: <EBEC3138-E799-4F0A-B9BE-9445F8A17E71@oracle.com> (raw)
Hi Linus-
The following changes since commit 4fc5f5346592cdc91689455d83885b0af65d71b8:
nfsd: fix using the correct variable for sizeof() (2022-03-20 12:49:38 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-5.18-1
for you to fetch changes up to 4d5004451ab2218eab94a30e1841462c9316ba19:
SUNRPC: Fix the svc_deferred_event trace class (2022-04-07 10:22:51 -0400)
----------------------------------------------------------------
NFSD bug fixes for 5.18-rc:
- Fix a write performance regression
- Fix crashes during request deferral on RDMA transports
----------------------------------------------------------------
Chuck Lever (2):
SUNRPC: Fix NFSD's request deferral on RDMA transports
SUNRPC: Fix the svc_deferred_event trace class
Haowen Bai (1):
SUNRPC: Return true/false (not 1/0) from bool functions
Trond Myklebust (2):
nfsd: Fix a write performance regression
nfsd: Clean up nfsd_file_put()
fs/nfsd/filecache.c | 25 +++++++++++++++----------
fs/nfsd/nfs2acl.c | 24 ++++++++++++------------
include/linux/sunrpc/svc.h | 1 +
include/trace/events/sunrpc.h | 7 ++++---
net/sunrpc/svc_xprt.c | 3 +++
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 2 +-
6 files changed, 36 insertions(+), 26 deletions(-)
--
Chuck Lever
next reply other threads:[~2022-04-12 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 22:21 Chuck Lever III [this message]
2022-04-13 1:24 ` 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=EBEC3138-E799-4F0A-B9BE-9445F8A17E71@oracle.com \
--to=chuck.lever@oracle.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®