linux-kernel - [GIT PULL] XFS fix for 3.11-rc3

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 25 Jul 2013 16:23:26 -0500 (CDT)
From:	bpm@....com (Ben Myers)
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	xfs@....sgi.com
Subject: [GIT PULL] XFS fix for 3.11-rc3

Hi Linus,

Please pull this fix for XFS in 3.11-rc3.  This resolves a regression
introduced in the 3.11-rc1 merge window with commit cca9f93a52d2 which
results in recovery corrupting filesystems after crashes.

Thanks,
	Ben

The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:

  Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs.git tags/for-linus-v3.11-rc3

for you to fetch changes up to e1b4271ac261b290fdab51446996fb13e68a57be:

  xfs: di_flushiter considered harmful (2013-07-25 10:41:42 -0500)

----------------------------------------------------------------
xfs: fix for 3.11-rc3

- fix for regression in commit cca9f93a52d2, recovery causing filesystem
  corruption after a crash

----------------------------------------------------------------
Dave Chinner (1):
      xfs: di_flushiter considered harmful

 fs/xfs/xfs_dinode.h      |  3 +++
 fs/xfs/xfs_inode.c       | 31 ++++++++++++++++++++++---------
 fs/xfs/xfs_log_recover.c | 13 +++++++++++--
 3 files changed, 36 insertions(+), 11 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/