linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull first round of NFS server -rc fixes for v5.7
Date: Thu, 23 Apr 2020 10:36:39 -0400	[thread overview]
Message-ID: <AC510313-C744-4F22-82F7-F75F20F4B073@oracle.com> (raw)

Hi Linus-

As promised, here is the first set of 5.7-rc fixes for NFS server issues.
These were all unresolved at the time the 5.7 window opened, and needed
some additional time to ensure they were correctly addressed. They are
ready now.

At the moment I know of one more urgent issue regarding the NFS server.
A fix has been tested and is under review. I expect to send one more
"5.7-rc fixes" PR, containing this fix (which now consists of 3 patches).


The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/cel/cel-2.6.git tags/nfsd-5.7-rc-1

for you to fetch changes up to 23cf1ee1f1869966b75518c59b5cbda4c6c92450:

  svcrdma: Fix leak of svc_rdma_recv_ctxt objects (2020-04-17 12:40:38 -0400)

----------------------------------------------------------------
Fixes:

- Address several use-after-free and memory leak bugs

- Prevent a backchannel livelock

----------------------------------------------------------------
Chuck Lever (3):
      SUNRPC: Fix backchannel RPC soft lockups
      svcrdma: Fix trace point use-after-free race
      svcrdma: Fix leak of svc_rdma_recv_ctxt objects

Vasily Averin (1):
      nfsd: memory corruption in nfsd4_lock()

Yihao Wu (1):
      SUNRPC/cache: Fix unsafe traverse caused double-free in cache_purge

 fs/nfsd/nfs4callback.c                     |  4 +++-
 fs/nfsd/nfs4state.c                        |  2 ++
 include/linux/sunrpc/svc_rdma.h            |  1 +
 include/trace/events/rpcrdma.h             | 50 ++++++++++++++++++++++++++++++++++++--------------
 net/sunrpc/cache.c                         |  5 +++--
 net/sunrpc/svc_xprt.c                      |  5 ++---
 net/sunrpc/svcsock.c                       |  4 ++++
 net/sunrpc/xprtrdma/svc_rdma_backchannel.c |  2 ++
 net/sunrpc/xprtrdma/svc_rdma_recvfrom.c    | 22 ++++++++++++++++++++++
 net/sunrpc/xprtrdma/svc_rdma_rw.c          |  3 +--
 net/sunrpc/xprtrdma/svc_rdma_sendto.c      | 29 ++++++++++++-----------------
 net/sunrpc/xprtrdma/svc_rdma_transport.c   |  5 -----
 net/sunrpc/xprtsock.c                      |  1 +
 13 files changed, 89 insertions(+), 44 deletions(-)

--
Chuck Lever




             reply	other threads:[~2020-04-23 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 14:36 Chuck Lever [this message]
2020-04-23 16:45 ` [GIT PULL] Please pull first round of NFS server -rc fixes for v5.7 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=AC510313-C744-4F22-82F7-F75F20F4B073@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).