linux-kernel - [GIT PULL] XFS update for 3.1-rc5

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, 02 Sep 2011 10:02:32 -0500
From:	Alex Elder <aelder@....com>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, xfs@....sgi.com,
	akpm@...ux-foundation.org
Subject: [GIT PULL] XFS update for 3.1-rc5

Linus, please pull the following XFS changes for 3.1-rc5.  The first
documents a feature that we plan to remove in 3.3.  The second fixes
a problem related to inode dirtying during unmount, and the third
fixes some other problems found in that region of code.

The last two have not been through a -next build because of the
recent kernel.org issues, but I've done testing with a local pull
into your current master branch and all looks well.

Thank you.

					-Alex

The following changes since commit 9e79e3e9dd9672b37ac9412e9a926714306551fe:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc (2011-08-30 11:28:18 -0700)

are available in the git repository at:

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

Christoph Hellwig (3):
      xfs: deprecate the nodelaylog mount option
      xfs: fix xfs_mark_inode_dirty during umount
      xfs: fix ->write_inode return values

 Documentation/feature-removal-schedule.txt |    8 ++++++
 fs/xfs/xfs_iops.c                          |   14 ++++++++--
 fs/xfs/xfs_super.c                         |   36 ++++++++-------------------
 3 files changed, 30 insertions(+), 28 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/