mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client fixes for 5.16
Date: Sat, 27 Nov 2021 15:32:01 +0000	[thread overview]
Message-ID: <8b451da7c237eae6e008f00cfc3b8aad6f5d8b67.camel@hammerspace.com> (raw)

Hi Linus,

The following changes since commit f96f8cc4a63dd645e07ea9712be4e0a76ea4ec1f:

  NFSv4: Sanity check the parameters in nfs41_update_target_slotid() (2021-11-07 09:23:14 -0500)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.16-2

for you to fetch changes up to 064a91771f7aae4ea2d13033b64e921951d216ce:

  SUNRPC: use different lock keys for INET6 and LOCAL (2021-11-22 17:44:49 -0500)

Thanks!
  Trond

----------------------------------------------------------------
NFS client bugfixes for Linux 5.16

Highlights include:

Stable fixes:
- NFSv42: Fix pagecache invalidation after COPY/CLONE

Bugfixes:
- NFSv42: Don't fail clone() just because the server failed to return
  post-op attributes
- SUNRPC: use different lockdep keys for INET6 and LOCAL
- NFSv4.1: handle NFS4ERR_NOSPC from CREATE_SESSION
- SUNRPC: fix header include guard in trace header

----------------------------------------------------------------
Benjamin Coddington (2):
      NFS: Add a tracepoint to show the results of nfs_set_cache_invalid()
      NFSv42: Fix pagecache invalidation after COPY/CLONE

NeilBrown (1):
      SUNRPC: use different lock keys for INET6 and LOCAL

Olga Kornievskaia (1):
      NFSv4.1: handle NFS4ERR_NOSPC by CREATE_SESSION

Thiago Rafael Becker (1):
      sunrpc: fix header include guard in trace header

Trond Myklebust (1):
      NFSv42: Don't fail clone() unless the OP_CLONE operation failed

 fs/nfs/inode.c                |  1 +
 fs/nfs/nfs42proc.c            |  4 +++-
 fs/nfs/nfs42xdr.c             |  3 +--
 fs/nfs/nfs4state.c            |  4 ++++
 fs/nfs/nfstrace.h             |  1 +
 include/trace/events/rpcgss.h |  2 +-
 net/sunrpc/xprtsock.c         | 10 +++++-----
 7 files changed, 16 insertions(+), 9 deletions(-)


-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2021-11-27 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 15:32 Trond Myklebust [this message]
2021-11-27 18:58 ` 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=8b451da7c237eae6e008f00cfc3b8aad6f5d8b67.camel@hammerspace.com \
    --to=trondmy@hammerspace.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®