From: Trond Myklebust <trondmy@gmail.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 3 more NFS client fixes...
Date: Thu, 14 Sep 2017 22:43:44 -0400 [thread overview]
Message-ID: <1505443424.11417.1.camel@gmail.com> (raw)
Hi Linus,
The following changes since commit 1bd5d6d08ea7ed0794c8a3908383d6d6fc202cdd:
NFS: Count the bytes of skipped subrequests in nfs_lock_and_join_requests() (2017-09-09 16:43:09 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.14-2
for you to fetch changes up to bf4b49059718b2217339eb15c60f8753d5b0da99:
NFS: various changes relating to reporting IO errors. (2017-09-11 22:28:56 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 4.14
Hightlights include:
bugfixes:
- Various changes relating to reporting IO errors.
- pnfs: Use the standard I/O stateid when calling LAYOUTGET
Features:
- Add static NFS I/O tracepoints for debugging
----------------------------------------------------------------
Chuck Lever (1):
NFS: Add static NFS I/O tracepoints
NeilBrown (1):
NFS: various changes relating to reporting IO errors.
Trond Myklebust (1):
pNFS: Use the standard I/O stateid when calling LAYOUTGET
fs/nfs/file.c | 16 ++--
fs/nfs/internal.h | 7 ++
fs/nfs/nfstrace.h | 248 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/nfs/pagelist.c | 4 +-
fs/nfs/pnfs.c | 14 +--
fs/nfs/read.c | 4 +
fs/nfs/write.c | 14 +--
7 files changed, 287 insertions(+), 20 deletions(-)
reply other threads:[~2017-09-15 2:43 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=1505443424.11417.1.camel@gmail.com \
--to=trondmy@gmail.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®