linux-kernel - XFS status update for October 2009

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, 12 Nov 2009 12:54:55 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	xfs@....sgi.com, linux-kernel@...r.kernel.org
Subject: XFS status update for October 2009

In October we saw the Linux 2.6.32 merge window with a major XFS update.
This update includes a refactoring of the inode allocator which also
allows for speedups for very large filesystems, major sync fixes, updates
to the fsync and O_SYNC handling which merge the two code paths into a single
and more efficient one, a workaround for the VFS time stamp behavior,
and of course various smaller fixes.  A couple of additional fixes have been
queued up for the next merge window.

On the userspace side there has been a healthy activity on xfsprogs:  mkfs can
now discard unused sectors on SSDs and thinly provisioned storage devices and
use the more generic libblkid for topology information and filesystems detection
instead of the older libdisk, and the build system gained some updates to
make the source package generation simpler and shared for different package
types.  A patch has been out to the list but yet committed to add symbol
versioning to the libhandle library to make future ABI additions easier.
The xfstests package only saw some minor activity with a new test case
and small build system fixes.

New minor releases of xfsprogs and xfsdump were tagged but not formally
released after additional discussion.  Instead a new major xfsprogs release
is planned for next month.
--
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/