From: Anna Schumaker <Anna.Schumaker@Netapp.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 a few more NFS client fixes for 4.13
Date: Fri, 28 Jul 2017 16:37:35 -0400 [thread overview]
Message-ID: <444eff18-a4fe-feb6-401f-e174b36a79dc@Netapp.com> (raw)
Hi Linus,
The following changes since commit 1ebf980127924c639e2b85c08468311ba1c95b70:
NFS/filelayout: Fix racy setting of fl->dsaddr in filelayout_check_deviceid() (2017-07-21 14:08:45 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.13-3
for you to fetch changes up to b7dbcc0e433f0f61acb89ed9861ec996be4f2b38:
NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter (2017-07-28 15:35:30 -0400)
----------------------------------------------------------------
Most of these fix locking bugs that Ben and Neil noticed, but I also have a patch to fix one more access bug that was reported after last week.
Stable fixes:
- Fix a race where CB_NOTIFY_LOCK fails to wake a waiter
- Invalidate file size when taking a lock to prevent corruption
Other fixes:
- Don't excessively generate tiny writes with fallocate
- Use the raw NFS access mask in nfs4_opendata_access()
Thanks,
Anna
----------------------------------------------------------------
Anna Schumaker (1):
NFS: Use raw NFS access mask in nfs4_opendata_access()
Benjamin Coddington (1):
NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter
NeilBrown (2):
NFS: invalidate file size when taking a lock.
NFS: Optimize fallocate by refreshing mapping when needed.
fs/nfs/file.c | 4 +++-
fs/nfs/nfs4proc.c | 14 +++++++++-----
2 files changed, 12 insertions(+), 6 deletions(-)
next reply other threads:[~2017-07-28 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 20:37 Anna Schumaker [this message]
2017-08-11 20:40 Anna Schumaker
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=444eff18-a4fe-feb6-401f-e174b36a79dc@Netapp.com \
--to=anna.schumaker@netapp.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®