linux-nfs.vger.kernel.org archive mirror
 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-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] please pull nfsd changes for 4.16
Date: Thu, 8 Feb 2018 17:58:04 -0500	[thread overview]
Message-ID: <20180208225804.GA17653@fieldses.org> (raw)

Please pull nfsd changes for 4.16 from

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

This request is late, apologies.

But it's also a fairly small update this time around.  Some cleanup,
RDMA fixes, overlayfs fixes, and a fix for an NFSv4 state bug.

The bigger deal for nfsd this time around is Jeff Layton's
already-merged i_version patches.  This series has a minor conflict with
that one, and the resolution should be obvious.  (Stephen Rothwell has
been carrying it in linux-next for what it's worth.)

--b.

Amir Goldstein (2):
      nfsd: encode stat->mtime for getattr instead of inode->i_mtime
      nfsd: store stat times in fill_pre_wcc() instead of inode times

Arnd Bergmann (1):
      NFSD: hide unused svcxdr_dupstr()

Benjamin Coddington (1):
      nfsd4: permit layoutget of executable-only files

Christoph Hellwig (1):
      sunrpc: remove dead code in svc_sock_setbufsize

Chuck Lever (2):
      svcrdma: Post Receives in the Receive completion handler
      svcrdma: Fix Read chunk round-up

Elena Reshetova (3):
      lockd: convert nsm_handle.sm_count from atomic_t to refcount_t
      lockd: convert nlm_lockowner.count from atomic_t to refcount_t
      lockd: convert nlm_rqst.a_count from atomic_t to refcount_t

J. Bruce Fields (2):
      nfsd4: don't set lock stateid's sc_type to CLOSED
      nfsd: return RESOURCE not GARBAGE_ARGS on too many ops

Trond Myklebust (1):
      nfsd: Detect unhashed stids in nfsd4_verify_open_stid()

 fs/lockd/clntproc.c                        | 14 +++++++-------
 fs/lockd/host.c                            |  2 +-
 fs/lockd/mon.c                             | 14 +++++++-------
 fs/lockd/svcproc.c                         |  2 +-
 fs/locks.c                                 |  6 ++----
 fs/nfsd/nfs3xdr.c                          | 31 +++++++++++++++++++++++++++++-
 fs/nfsd/nfs4proc.c                         |  9 ++++++---
 fs/nfsd/nfs4state.c                        |  6 ++----
 fs/nfsd/nfs4xdr.c                          | 16 +++++++++------
 fs/nfsd/nfsfh.h                            | 28 ++++++---------------------
 fs/nfsd/nfsxdr.c                           |  1 +
 include/linux/lockd/lockd.h                |  6 +++---
 include/linux/sunrpc/svc_rdma.h            |  2 --
 net/sunrpc/svcsock.c                       | 14 --------------
 net/sunrpc/xprtrdma/svc_rdma_backchannel.c |  5 -----
 net/sunrpc/xprtrdma/svc_rdma_recvfrom.c    |  9 +--------
 net/sunrpc/xprtrdma/svc_rdma_rw.c          | 12 ++++++++----
 net/sunrpc/xprtrdma/svc_rdma_sendto.c      |  6 ------
 net/sunrpc/xprtrdma/svc_rdma_transport.c   | 25 +++++++-----------------
 19 files changed, 92 insertions(+), 116 deletions(-)

                 reply	other threads:[~2018-02-08 22:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180208225804.GA17653@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).