linux-kernel - [GIT PULL v2] xfs: fixes for 4.5-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 11 Mar 2016 11:23:23 +1100
From:	Dave Chinner <david@...morbit.com>
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	xfs@....sgi.com
Subject: [GIT PULL v2] xfs: fixes for 4.5-rc7 

[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@...morbit.com