linux-kernel - [GIT PULL] XFS update for 3.2

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:	Thu, 29 Dec 2011 11:31:39 -0600
From:	Ben Myers <bpm@....com>
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, xfs@....sgi.com,
	linux-kernel@...r.kernel.org
Subject: [GIT PULL] XFS update for 3.2

Hi Linus,

Please pull the following fixes for 3.2.  Quoting Christoph Hellwig:
"These two small fixes fix issues with periodic metadata writeback and
sync not being able [to] write file size updates to disk in some cases."
These have not gone through -next because we have 3.3 work in the
oss/master branch right now, but they merged and built cleanly on
3.2-rc7.  They have been tested thoroughly by Mark Tinguely and myself.
It is late in the cycle and I will submit them later for 3.2-stable if
you prefer.

Have a happy New Year!

Thanks,
       Ben

The following changes since commit 371de6e4e0042adf4f9b54c414154f57414ddd37:
  Keith Packard (1):
        drm/i915: Disable RC6 on Sandybridge by default

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs for-linus

Christoph Hellwig (2):
      xfs: log the inode in ->write_inode calls for kupdate
      xfs: log all dirty inodes in xfs_fs_sync_fs

 fs/xfs/xfs_super.c |   30 +++++-------------------------
 fs/xfs/xfs_sync.c  |   36 ++++++++++++++++++++++++++++++++++++
 fs/xfs/xfs_sync.h  |    2 ++
 3 files changed, 43 insertions(+), 25 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/