mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
	Linux linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT Pull] Please pull more NFS client bug fixes
Date: Wed, 8 May 2013 23:23:07 +0000	[thread overview]
Message-ID: <1368055385.3282.25.camel@leira.trondhjem.org> (raw)

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

The following changes since commit 721ccfb79b6f74f4052de70236d24047e73682d4:

  NFSv4: Warn once about servers that incorrectly apply open mode to setattr (2013-04-29 11:11:58 -0400)

are available in the git repository at:

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

for you to fetch changes up to c23266d532b4de796a346f57a66587c5db17d27e:

  NFS4.1 Fix data server connection race (2013-05-08 17:19:32 -0400)

----------------------------------------------------------------
More NFS client bugfixes for 3.10

- Ensure that we match the 'sec=' mount flavour against the server list
- Fix the NFSv4 byte range locking in the presence of delegations
- Ensure that we conform to the NFSv4.1 spec w.r.t. freeing lock stateids
- Fix a pNFS data server connection race

----------------------------------------------------------------
Andy Adamson (1):
      NFS4.1 Fix data server connection race

Trond Myklebust (4):
      NFSv4.x: Fix handling of partially delegated locks
      SUNRPC: Don't spam syslog with "Pseudoflavor not found" messages
      NFSv4: Convert nfs41_free_stateid to use an asynchronous RPC call
      NFSv4.1: Ensure that we free the lock stateid on the server

Weston Andros Adamson (1):
      NFSv3: match sec= flavor against server list

 fs/nfs/nfs4_fs.h               |   3 +-
 fs/nfs/nfs4filelayout.h        |   2 +
 fs/nfs/nfs4filelayoutdev.c     |  26 ++++++++-
 fs/nfs/nfs4proc.c              | 119 +++++++++++++++++++++++++++++++----------
 fs/nfs/nfs4state.c             |  11 ++--
 fs/nfs/nfs4xdr.c               |   2 +-
 fs/nfs/super.c                 |  48 ++++++++++++++---
 include/linux/nfs_xdr.h        |   2 +-
 net/sunrpc/auth_gss/auth_gss.c |   3 +-
 net/sunrpc/clnt.c              |   2 +-
 10 files changed, 172 insertions(+), 46 deletions(-)

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

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

                 reply	other threads:[~2013-05-08 23:23 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=1368055385.3282.25.camel@leira.trondhjem.org \
    --to=trond.myklebust@netapp.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®