From: Dave Chinner <david@fromorbit.com>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] xfs: fixes for 3.17-rc3
Date: Sat, 6 Sep 2014 10:07:11 +1000 [thread overview]
Message-ID: <20140906000711.GX20518@dastard> (raw)
Hi Linus,
Can you please pull the following XFS fixes? The fixes all address
recently discovered data corruption issues. The original Direct IO
issue was discovered by Chris Mason @ Facebook on a production
workload which mixed buffered reads with direct reads and writes IO
to the same file. The fix for that exposed other issues with page
invalidation (exposed by millions of fsx operations) failing due to
dirty buffers beyond EOF.
Finally, the collapse_range code could also cause problems due to
racing writeback changing the extent map while it was being shifted
around. The commits for that problem are simple mitigation fixes
that prevent the problem from occuring. A more robust fix for 3.18
that addresses the underlying problem is currently being worked on
by Brian.
-Dave.
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs tags/xfs-for-linus-3.17-rc3
for you to fetch changes up to 41b9d7263ea1e270019c5d04fa0ab15db50b9725:
xfs: trim eofblocks before collapse range (2014-09-02 12:12:53 +1000)
----------------------------------------------------------------
xfs: fixes for v3.17-rc3
Fix:
- a direct IO read/buffered read data corruption
- the associated fallout from the DIO data corruption fix
- collapse range bugs that are potential data corruption issues.
----------------------------------------------------------------
Brian Foster (2):
xfs: don't log inode unless extent shift makes extent modifications
xfs: trim eofblocks before collapse range
Chris Mason (1):
xfs: don't zero partial page cache pages during O_DIRECT writes
Dave Chinner (4):
xfs: don't dirty buffers beyond EOF
xfs: don't zero partial page cache pages during O_DIRECT writes
xfs: use ranged writeback and invalidation for direct IO
xfs: xfs_file_collapse_range is delalloc challenged
fs/xfs/libxfs/xfs_bmap.c | 18 ++++++++------
fs/xfs/xfs_aops.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_bmap_util.c | 20 +++++++++++++++
fs/xfs/xfs_file.c | 27 +++++++++++++++++---
4 files changed, 114 insertions(+), 12 deletions(-)
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-09-06 0:07 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=20140906000711.GX20518@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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