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 v2] xfs: fixes for 4.5-rc7
Date: Fri, 11 Mar 2016 11:23:23 +1100 [thread overview]
Message-ID: <20160311002323.GB11812@dastard> (raw)
[v2 - now with correct cc list. Sorry for the dup, Linus]
Hi Linus,
Can you please pull the XFS fixes from the tag below? This is a fix
for a regression introduced in 4.5-rc1 by the new torn log write
detection code. The regression only affects people moving a clean
filesystem between machines/kernels of different architecture (such
as changing between 32 bit and 64 bit kernels), but this is the
recommended (and only!) safe way to migrate a filesystem between
architectures so we really need to ensure it works.
The changes are larger than I'd prefer right at the end of the
release cycle, but the majority of the change is just factoring
code to enable the detection of a clean log at the correct time to
avoid this issue.
Thanks!
-Dave.
The following changes since commit 36f90b0a2ddd60823fe193a85e60ff1906c2a9b3:
Linux 4.5-rc2 (2016-01-31 18:12:16 -0800)
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.5-rc7
for you to fetch changes up to 7f6aff3a29b08fc4234c8136eb1ac31b4897522c:
xfs: only run torn log write detection on dirty logs (2016-03-07 08:22:22 +1100)
----------------------------------------------------------------
xfs: fixes for 4.5-rc7
Changes:
o Only perform torn log write detection on dirty logs. This prevents
failures being detected due to a clean filesystem being moved
between machines or kernels of different architectures (e.g. 32
-> 64 bit, BE -> LE, etc). This fixes a regression introduced by
the torn log write detection in 4.5-rc1.
----------------------------------------------------------------
Brian Foster (4):
xfs: separate log head record discovery from verification
xfs: refactor unmount record detection into helper
xfs: refactor in-core log state update to helper
xfs: only run torn log write detection on dirty logs
fs/xfs/xfs_log_recover.c | 271 ++++++++++++++++++++++++++++------------------
1 file changed, 168 insertions(+), 103 deletions(-)
--
Dave Chinner
david@fromorbit.com
reply other threads:[~2016-03-11 0:23 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=20160311002323.GB11812@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
all inboxes | Powered by JetHome®