Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes for Linux 3.16
Date: Wed, 25 Jun 2014 18:52:05 -0400	[thread overview]
Message-ID: <1403736725.3457.1.camel@leira.trondhjem.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

Hi Linus,

The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:

  Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)

are available in the git repository at:

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

for you to fetch changes up to 66b068604903849c5dee3842eb72564064c64c72:

  NFSv4: test SECINFO RPC_AUTH_GSS pseudoflavors for support (2014-06-24 18:46:58 -0400)

----------------------------------------------------------------
NFS client fixes for Linux 3.16

Highlights include:

- Stable fix for a data corruption case due to incorrect cache validation
- Fix a couple of false positive cache invalidations
- Fix NFSv4 security negotiation issues

----------------------------------------------------------------
Andy Adamson (3):
      NFS check the return of nfs4_negotiate_security in nfs4_submount
      NFS Return -EPERM if no supported or matching SECINFO flavor
      NFSv4: test SECINFO RPC_AUTH_GSS pseudoflavors for support

Scott Mayhew (1):
      nfs: Fix cache_validity check in nfs_write_pageuptodate()

Trond Myklebust (2):
      NFS: Clear NFS_INO_REVAL_PAGECACHE when we update the file size
      NFS: Don't mark the data cache as invalid if it has been flushed

 fs/nfs/inode.c         |  76 +++++++++++++++++++-----------------
 fs/nfs/nfs4_fs.h       |   2 +-
 fs/nfs/nfs4namespace.c | 102 +++++++++++++++++++++++++++----------------------
 fs/nfs/nfs4proc.c      |   2 +-
 fs/nfs/write.c         |   4 +-
 net/sunrpc/auth.c      |   1 +
 6 files changed, 104 insertions(+), 83 deletions(-)

-- 
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2014-06-25 22:52 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=1403736725.3457.1.camel@leira.trondhjem.org \
    --to=trond.myklebust@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