From: Trond Myklebust <trondmy@primarydata.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 changes
Date: Mon, 9 Oct 2017 17:35:36 +0000 [thread overview]
Message-ID: <1507570534.25956.1.camel@primarydata.com> (raw)
Hi Linus,
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-rc3 (2017-10-01 14:54:54 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.14-3
for you to fetch changes up to e8fa33a6f6c7688591542db955794b69b8cecc55:
NFSv4/pnfs: Fix an infinite layoutget loop (2017-10-04 14:06:54 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 4.14
Hightlights include:
stable fixes:
- nfs/filelayout: fix oops when freeing filelayout segment
- NFS: Fix uninitialized rpc_wait_queue
bugfixes:
- NFSv4/pnfs: Fix an infinite layoutget loop
- nfs: RPC_MAX_AUTH_SIZE is in bytes
----------------------------------------------------------------
Benjamin Coddington (1):
NFS: Fix uninitialized rpc_wait_queue
Colin Ian King (1):
sunrpc: remove redundant initialization of sock
Dan Carpenter (1):
NFS: Cleanup error handling in nfs_idmap_request_key()
J. Bruce Fields (1):
nfs: RPC_MAX_AUTH_SIZE is in bytes
Scott Mayhew (1):
nfs/filelayout: fix oops when freeing filelayout segment
Trond Myklebust (1):
NFSv4/pnfs: Fix an infinite layoutget loop
fs/nfs/client.c | 2 +-
fs/nfs/filelayout/filelayout.c | 3 ++-
fs/nfs/nfs4idmap.c | 2 +-
fs/nfs/nfs4proc.c | 3 +--
fs/nfs/nfs4xdr.c | 4 ++--
net/sunrpc/xprtsock.c | 2 +-
6 files changed, 8 insertions(+), 8 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next reply other threads:[~2017-10-09 17:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:35 Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 17:30 [GIT PULL] Please pull NFS client changes Trond Myklebust
2022-04-08 17:46 ` pr-tracker-bot
2018-12-06 21:55 Trond Myklebust
2018-12-07 18:35 ` pr-tracker-bot
2018-11-25 3:04 Trond Myklebust
2018-11-25 17:45 ` pr-tracker-bot
2018-01-30 14:39 Trond Myklebust
2016-01-14 21:09 Trond Myklebust
2015-09-07 20:59 Trond Myklebust
2015-09-08 1:59 ` Stephen Rothwell
2015-09-08 6:01 ` Christoph Hellwig
2015-09-11 16:27 ` Christoph Hellwig
2015-09-11 17:06 ` Trond Myklebust
2014-12-08 3:09 Trond Myklebust
2014-10-06 13:03 Trond Myklebust
2014-07-19 20:07 Trond Myklebust
2014-01-27 16:49 Trond Myklebust
2011-10-25 12:25 Trond Myklebust
2011-07-27 18:40 [GIT PULL] Please pull nfs " Trond Myklebust
2011-03-17 17:19 [GIT PULL] Please pull NFS " Trond Myklebust
2011-01-11 23:08 Trond Myklebust
2010-08-06 18:26 Trond Myklebust
2010-05-17 22:28 Trond Myklebust
2010-05-18 8:59 ` Lukas Hejtmanek
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=1507570534.25956.1.camel@primarydata.com \
--to=trondmy@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;
as well as URLs for NNTP newsgroup(s).