mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Torvalds Linus <torvalds@linux-foundation.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client fixes
Date: Wed, 19 Feb 2014 09:40:28 -0500	[thread overview]
Message-ID: <5B5733C1-4A37-4B3F-9B28-2CAA88C5C844@primarydata.com> (raw)
In-Reply-To: <1392819180.3670.1.camel@leira.trondhjem.org>


On Feb 19, 2014, at 9:13, Trond Myklebust <trond.myklebust@primarydata.com> wrote:

> Hi Linus,
> 
> The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed:
> 
>  Linux 3.14-rc2 (2014-02-09 18:15:47 -0800)
> 
> are available in the git repository at:
> 
>  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.14-4
> 
> for you to fetch changes up to 2564f0dc58962a08abc960fca820e344f61981ed:

Doh… The very last patch in the series was misapplied. I’ve fixed it up and pushed out a new tag using —force. It being 6:40 am in Oregon, hopefully you still haven’t applied the bad patch…

nfs-for-3.14-4 should now point to commit 146d70caaa1b87f64597743429d7da4b8073d0c9, which has Andy’s patch applied correctly.

Apologies…
  Trond

> 
>  NFS fix error return in nfs4_select_rw_stateid (2014-02-18 11:33:03 -0500)
> 
> ----------------------------------------------------------------
> NFS client bugfixes for Linux 3.14
> 
> Highlights include stable fixes for the following bugs:
> 
> - General performance regression due to NFS_INO_INVALID_LABEL being set
>  when the server doesn't support labeled NFS
> - Hang in the RPC code due to a socket out-of-buffer race
> - Infinite loop when trying to establish the NFSv4 lease
> - Use-after-free bug in the RPCSEC gss code.
> - nfs4_select_rw_stateid is returning with a non-zero error value on success
> 
> Other bug fixes:
> 
> - Potential memory scribble in the RPC bi-directional RPC code
> - Pipe version reference leak
> - Use the correct net namespace in the new NFSv4 migration code
> 
> ----------------------------------------------------------------
> Andy Adamson (1):
>      NFS fix error return in nfs4_select_rw_stateid
> 
> Trond Myklebust (7):
>      NFS: Do not set NFS_INO_INVALID_LABEL unless server supports labeled NFS
>      SUNRPC: Don't create a gss auth cache unless rpc.gssd is running
>      SUNRPC: Fix races in xs_nospace()
>      SUNRPC: Fix potential memory scribble in xprt_free_bc_request()
>      SUNRPC: Ensure that gss_auth isn't freed before its upcall messages
>      SUNRPC: Fix a pipe_version reference leak
>      NFSv4: Use the correct net namespace in nfs4_update_server
> 
> fs/nfs/inode.c                 | 14 ++++++++++----
> fs/nfs/internal.h              | 12 +++++++++++-
> fs/nfs/nfs4client.c            |  7 ++++---
> fs/nfs/nfs4namespace.c         | 12 ++++++------
> fs/nfs/nfs4state.c             |  1 +
> net/sunrpc/auth_gss/auth_gss.c | 19 ++++++++++++++++---
> net/sunrpc/backchannel_rqst.c  |  6 ++++--
> net/sunrpc/xprtsock.c          |  6 +++++-
> 8 files changed, 57 insertions(+), 20 deletions(-)
> 
> -- 
> Trond Myklebust
> Linux NFS client maintainer, PrimaryData
> trond.myklebust@primarydata.com
> 

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


  reply	other threads:[~2014-02-19 14:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 14:13 Trond Myklebust
2014-02-19 14:40 ` Trond Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-26 20:12 Trond Myklebust
2019-03-26 22:25 ` pr-tracker-bot
2017-10-24 22:56 Trond Myklebust
2016-09-12 19:28 Trond Myklebust
2016-02-23 18:33 Trond Myklebust
2014-09-12 17:04 Trond Myklebust
2014-08-29 19:35 Trond Myklebust
2014-08-25 14:55 Trond Myklebust
2014-02-04 16:52 Trond Myklebust
2013-07-19 19:27 Myklebust, Trond
2013-04-10 15:59 Myklebust, Trond
2013-01-31 19:47 Myklebust, Trond
2012-08-22 15:41 Myklebust, Trond
2011-06-21 18:36 Trond Myklebust
2010-12-10 18:05 Trond Myklebust
2010-12-09  3:11 Trond Myklebust
2010-04-13 21:54 Trond Myklebust

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=5B5733C1-4A37-4B3F-9B28-2CAA88C5C844@primarydata.com \
    --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

all inboxes | Powered by JetHome®