From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client fixes
Date: Tue, 26 Mar 2019 20:12:07 +0000 [thread overview]
Message-ID: <938c564de7930769feacf1403fae0c9511f10993.camel@hammerspace.com> (raw)
Hi Linus,
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.1-3
for you to fetch changes up to 01f2f5b82a2b523ae76af53f2ff43c48dde10a00:
SUNRPC: fix uninitialized variable warning (2019-03-26 13:04:32 -0700)
----------------------------------------------------------------
NFS client bugfixes for Linux 5.1
Highlights include:
Stable fixes:
- Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
- fix mount/umount race in nlmclnt.
- NFSv4.1 don't free interrupted slot on open
Bugfixes:
- Don't let RPC_SOFTCONN tasks time out if the transport is connected
- Fix a typo in nfs_init_timeout_values()
- Fix layoutstats handling during read failovers
- fix uninitialized variable warning
----------------------------------------------------------------
Alakesh Haloi (1):
SUNRPC: fix uninitialized variable warning
Catalin Marinas (1):
NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
NeilBrown (1):
NFS: fix mount/umount race in nlmclnt.
Olga Kornievskaia (1):
NFSv4.1 don't free interrupted slot on open
Trond Myklebust (3):
SUNRPC: Don't let RPC_SOFTCONN tasks time out if the transport is connected
NFS: Fix a typo in nfs_init_timeout_values()
pNFS/flexfiles: Fix layoutstats handling during read failovers
fs/lockd/host.c | 3 +--
fs/nfs/client.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 5 ++++-
fs/nfs/nfs4proc.c | 5 ++---
net/sunrpc/clnt.c | 12 +++++++++++-
net/sunrpc/xprtsock.c | 4 ++--
6 files changed, 21 insertions(+), 10 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2019-03-26 20:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 20:12 Trond Myklebust [this message]
2019-03-26 22:25 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
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-19 14:13 Trond Myklebust
2014-02-19 14:40 ` 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=938c564de7930769feacf1403fae0c9511f10993.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®