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: updates for 4.2-rc4
Date: Fri, 31 Jul 2015 12:03:29 +1000 [thread overview]
Message-ID: <20150731020329.GO16638@dastard> (raw)
Hi Linus,
Can you please pull the XFS fixes from the tag below? There are a
couple of recently found, long standing remote attribute corruption
fixes caused by log recovery getting confused after a crash, and the
new DAX code in XFS (merged in 4.2-rc1) needs to actually use the
DAX fault path on read faults.
Thanks!
-Dave.
The following changes since commit bc0195aad0daa2ad5b0d76cce22b167bc3435590:
Linux 4.2-rc2 (2015-07-12 15:10:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git tags/xfs-for-linus-4.2-rc4
for you to fetch changes up to df150ed102baa0e78c06e08e975dfb47147dd677:
xfs: remote attributes need to be considered data (2015-07-29 11:48:02 +1000)
----------------------------------------------------------------
xfs: updates for 4.2-rc4
- remote attribute log recovery corruption fixes
- DAX page faults need to use direct mappings, not a page cache
mapping.
----------------------------------------------------------------
Dave Chinner (3):
xfs: call dax_fault on read page faults for DAX
xfs: remote attribute headers contain an invalid LSN
xfs: remote attributes need to be considered data
fs/dax.c | 14 +++++++++++--
fs/xfs/libxfs/xfs_attr_remote.c | 44 ++++++++++++++++++++++++++++++---------
fs/xfs/xfs_file.c | 21 +++++++++++++------
fs/xfs/xfs_log_recover.c | 11 +++++++---
4 files changed, 69 insertions(+), 21 deletions(-)
--
Dave Chinner
david@fromorbit.com
reply other threads:[~2015-07-31 2: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=20150731020329.GO16638@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