linux-kernel - XFS status update for August 2012

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, 13 Sep 2012 04:04:20 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	xfs@....sgi.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: XFS status update for August 2012

After the release of Linux 3.5 in July, August saw the big XFS merge for
the Linux 3.6 merge window.  In the meantime the XFS tree has seen low
activity, with refined support for SEEK_HOLE/SEEK_DATA that takes unwritten
extents into account as the main feature.  A couple of fixes also went in
and mostly got back ported to mainline for Linux 3.5 as well.

The mailing list had a lot of traffic about interesting updates that didn't
make it into the tree yet, with the most interesting being: remount support
for the inode64 option, a patch series allowing to trim back large
preallocations when the filesystem is out of space, and a large rewrite
of the XFS-internal sync code.

On the user land side xfs_db saw a fix for a very long standing bug go into
the tree and xfstests saw a few fixes.  The mailing list list saw various other
interesting updates including a German translation for the xfsdump messages,
32-bit project ID support in xfsdump, a lot of xfstests updates including a
patch to use the upstream util-linux version of fstrim in xfstests, support
for tmpfs in xfstests, various ext3 and btrfs updates, but none of them
made it into the git tree.  There also was a lot of discussion of older
patch to reorganize the xfstests source tree.
--
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/