public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@primarydata.com>
Subject: [GIT PULL] nfsd changes for 4.6
Date: Thu, 24 Mar 2016 09:35:51 -0400	[thread overview]
Message-ID: <20160324133551.GA21950@fieldses.org> (raw)

Please pull nfsd changes for 4.6 from

  git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.6

----------------------------------------------------------------
Various bugfixes, a RDMA update from Chuck Lever, and support for a new
pnfs layout type from Christoph Hellwig.  The new layout type is a
variant of the block layout which uses SCSI features to offer improved
fencing and device identification.

(Also: note this pull request also includes the client side of SCSI
layout, with Trond's permission.)

----------------------------------------------------------------
Chuck Lever (14):
      nfsd: Update NFS server comments related to RDMA support
      svcrdma: Find client-provided write and reply chunks once per reply
      svcrdma: Do not write xdr_buf::tail in a Write chunk
      svcrdma: Do not send Write chunk XDR pad with inline content
      nfsd: Lower NFSv4.1 callback message size limit
      svcrdma: Close connection when a send error occurs
      svcrdma: svc_rdma_post_recv() should close connection on error
      rpcrdma: Add RPCRDMA_HDRLEN_ERR
      svcrdma: Make RDMA_ERROR messages work
      svcrdma: Use correct XID in error replies
      svcrdma: Hook up the logic to return ERR_CHUNK
      svcrdma: Remove close_out exit path
      svcrdma: Use new CQ API for RPC-over-RDMA server receive CQs
      svcrdma: Use new CQ API for RPC-over-RDMA server send CQs

J. Bruce Fields (3):
      nfsd4: fix bad bounds checking
      nfsd4: resfh unused in nfsd4_secinfo
      nfsd: fix deadlock secinfo+readdir compound

Kinglong Mee (1):
      nfsd: Fix a memory leak when meeting unsupported state_protect_how4

NeilBrown (1):
      sunrpc/cache: drop reference when sunrpc_cache_pipe_upcall() detects a race

Sudip Mukherjee (1):
      nfsd: recover: fix memory leak

 fs/nfsd/nfs4proc.c                         |   3 +-
 fs/nfsd/nfs4recover.c                      |   1 +
 fs/nfsd/nfs4state.c                        |  29 +-
 fs/nfsd/nfs4xdr.c                          |  15 +-
 include/linux/sunrpc/auth.h                |   7 +
 include/linux/sunrpc/rpc_rdma.h            |   1 +
 include/linux/sunrpc/svc_rdma.h            |  20 +-
 net/sunrpc/auth_null.c                     |   4 +-
 net/sunrpc/auth_unix.c                     |   6 +-
 net/sunrpc/cache.c                         |   6 +-
 net/sunrpc/xprtrdma/svc_rdma_backchannel.c |  17 +-
 net/sunrpc/xprtrdma/svc_rdma_marshal.c     |  64 +++--
 net/sunrpc/xprtrdma/svc_rdma_recvfrom.c    |  60 ++--
 net/sunrpc/xprtrdma/svc_rdma_sendto.c      | 196 +++++++++----
 net/sunrpc/xprtrdma/svc_rdma_transport.c   | 445 ++++++++++-------------------
 15 files changed, 408 insertions(+), 466 deletions(-)

             reply	other threads:[~2016-03-24 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 13:35 J. Bruce Fields [this message]
2016-03-24 19:00 ` [GIT PULL] nfsd changes for 4.6 Trond Myklebust
2016-03-24 19:10   ` J. Bruce Fields

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=20160324133551.GA21950@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@primarydata.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