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>,
LKML <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@redhat.com>
Subject: [GIT PULL] nfsd fixes for 5.19
Date: Sat, 11 Jun 2022 00:17:34 +0000 [thread overview]
Message-ID: <FF9D9B25-0117-446D-B5B3-A4240C67A99F@oracle.com> (raw)
Hi Linus-
The following changes since commit 08af54b3e5729bc1d56ad3190af811301bdc37a1:
NFSD: nfsd_file_put() can sleep (2022-05-26 10:50:51 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-5.19-1
for you to fetch changes up to da9e94fe000e11f21d3d6f66012fe5c6379bd93c:
SUNRPC: Remove pointer type casts from xdr_get_next_encode_buffer() (2022-06-08 12:39:37 -0400)
----------------------------------------------------------------
Notable changes:
- There is now a backup maintainer for NFSD
Notable fixes:
- Prevent array overruns in svc_rdma_build_writes()
- Prevent buffer overruns when encoding NFSv3 READDIR results
- Fix a potential UAF in nfsd_file_put()
----------------------------------------------------------------
Chuck Lever (7):
NFSD: Fix potential use-after-free in nfsd_file_put()
SUNRPC: Trap RDMA segment overflows
SUNRPC: Fix the calculation of xdr->end in xdr_get_next_encode_buffer()
SUNRPC: Optimize xdr_reserve_space()
SUNRPC: Clean up xdr_commit_encode()
SUNRPC: Clean up xdr_get_next_encode_buffer()
SUNRPC: Remove pointer type casts from xdr_get_next_encode_buffer()
Jeff Layton (1):
MAINTAINERS: reciprocal co-maintainership for file locking and nfsd
MAINTAINERS | 2 ++
fs/nfsd/filecache.c | 9 +++++----
include/linux/sunrpc/xdr.h | 16 +++++++++++++++-
net/sunrpc/xdr.c | 37 +++++++++++++++++++++++--------------
net/sunrpc/xprtrdma/svc_rdma_rw.c | 4 ++--
5 files changed, 47 insertions(+), 21 deletions(-)
--
Chuck Lever
next reply other threads:[~2022-06-11 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 0:17 Chuck Lever III [this message]
2022-06-11 0:38 ` 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=FF9D9B25-0117-446D-B5B3-A4240C67A99F@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®