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 changes
Date: Sat, 19 Jul 2014 16:07:02 -0400 [thread overview]
Message-ID: <1405800422.3254.4.camel@leira.trondhjem.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
Hi Linus,
Apologies for the relative lateness of this pull request, however the
commits fix some issues with the NFS read/write code updates in 3.16-rc1
that can cause serious Oopsing when using small r/wsize. The delay was
mainly due to extra testing to make sure that the fixes behave
correctly.
The following changes since commit 66b068604903849c5dee3842eb72564064c64c72:
NFSv4: test SECINFO RPC_AUTH_GSS pseudoflavors for support (2014-06-24 18:46:58 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.16-3
for you to fetch changes up to f563b89b182594f827b4100bd34f916339785a77:
NFS: Don't reset pg_moreio in __nfs_pageio_add_request (2014-07-13 15:18:44 -0400)
----------------------------------------------------------------
NFS client fixes for Linux 3.16
Highlights include;
- Stable fix for an NFSv3 posix ACL regression
- Multiple fixes for regressions to the NFS generic read/write code
- Fix page splitting bugs that come into play when a small rsize/wsize
read/write needs to be sent again (due to error conditions or page
redirty).
- Fix nfs_wb_page_cancel, which is called by the "invalidatepage" method
- Fix 2 compile warnings about unused variables.
- Fix a performance issue affecting unstable writes.
----------------------------------------------------------------
Christoph Hellwig (1):
nfs: only show Posix ACLs in listxattr if actually present
Trond Myklebust (2):
NFS: Remove 2 unused variables
NFS: Don't reset pg_moreio in __nfs_pageio_add_request
Weston Andros Adamson (5):
nfs: mark nfs_page reqs with flag for extra ref
nfs: nfs_page should take a ref on the head req
nfs: change find_request to find_head_request
nfs: handle multiple reqs in nfs_page_async_flush
nfs: handle multiple reqs in nfs_wb_page_cancel
fs/nfs/direct.c | 2 -
fs/nfs/internal.h | 1 +
fs/nfs/nfs3acl.c | 43 +++++++
fs/nfs/nfs3proc.c | 4 +-
fs/nfs/pagelist.c | 20 +++-
fs/nfs/write.c | 335 +++++++++++++++++++++++++++++++++++++++++++++---------
6 files changed, 343 insertions(+), 62 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-07-19 20:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 20:07 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
2017-10-09 17:35 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-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=1405800422.3254.4.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).