From: Trond Myklebust <trond.myklebust@primarydata.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 NFS client fixes
Date: Mon, 25 Aug 2014 10:55:30 -0400 [thread overview]
Message-ID: <1408978530.6599.1.camel@leira.trondhjem.org> (raw)
Hi Linus,
The following changes since commit 451fd72219dd6f3355e2d036c598544c760ee532:
Merge tag 'pwm/for-3.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm (2014-08-22 14:50:21 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.17-2
for you to fetch changes up to 92a56555bd576c61b27a5cab9f38a33a1e9a1df5:
nfs: Don't busy-wait on SIGKILL in __nfs_iocounter_wait (2014-08-22 18:04:44 -0400)
----------------------------------------------------------------
NFS client fixes for 3.17
Highlights:
- More fixes for read/write codepath regressions
- Sleeping while holding the inode lock
- Stricter enforcement of page contiguity when coalescing requests
- Fix up error handling in the page coalescing code
- Don't busy wait on SIGKILL in the file locking code
----------------------------------------------------------------
David Jeffery (1):
nfs: Don't busy-wait on SIGKILL in __nfs_iocounter_wait
Weston Andros Adamson (7):
nfs: change nfs_page_group_lock argument
nfs: fix nonblocking calls to nfs_page_group_lock
nfs: use blocking page_group_lock in add_request
nfs: fix error handling in lock_and_join_requests
nfs: don't sleep with inode lock in lock_and_join_requests
nfs: disallow duplicate pages in pgio page vectors
nfs: can_coalesce_requests must enforce contiguity
fs/nfs/pagelist.c | 84 ++++++++++++++++++++++++++++++++++--------------
fs/nfs/write.c | 21 +++++++++---
include/linux/nfs_page.h | 1 +
3 files changed, 77 insertions(+), 29 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next reply other threads:[~2014-08-25 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 14:55 Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 20:12 [GIT PULL] Please pull NFS client fixes 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-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=1408978530.6599.1.camel@leira.trondhjem.org \
--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;
as well as URLs for NNTP newsgroup(s).