linux-kernel - XFS status update for August 2008

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:	Sun, 31 Aug 2008 19:10:56 +0200
From:	Christoph Hellwig <hch@....de>
To:	xfs@....sgi.com, linux-kernel@...r.kernel.org
Subject: XFS status update for August 2008

With the 2.6.27-rc5 release the 2.6.27 cycle is nearing it's end.  The major
XFS feature in 2.6.27-rc5 is support for case-insensitive file names.  At
this point it is still limited to 7bit ASCII file names, with updates for
utf8 file names expected to follow later.  In addition to that 2.6.27-rc5
fixes a long-standing problem with non-EABI arm compiler which pack some XFS
data structures wrongly.  Besides this 2.6.27-rc5 also contains various
cleanups, most notably the removal of the last bhv_vnode_t instances, and
most uses of semaphores.  As usual the diffstat for XFS from 2.6.26 to
2.6.26-rc5 is negative:

	 100 files changed, 3819 insertions(+), 4409 deletions(-)

On the user space front a new minor xfsprogs version is about to be released
containing various fixes including the user space part of arm packing fix.

Work in progress on the XFS mailing list are a large patch set to unify the
alloc, inobt and bmap btree implementation into a single that supports
arbitrarily pluggable key and record formats.  These btree changes are the
first major preparation for adding CRC checks to all metadata structures in
XFS, and an even larger patch set to unify the XFS and Linux inode structures,
and perform all inode write back from the btree uses instead of an inode
cache in XFS.
--
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/