linux-kernel - XFS status update for April 2010

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]

Message-ID: <20100508190843.GA20445@infradead.org>
Date:	Sat, 8 May 2010 15:08:43 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	xfs@....sgi.com, linux-kernel@...r.kernel.org
Subject: XFS status update for April 2010

In April 2.6.34 still was in the release candidate phase, with
a hand full of XFS fixes making it into mainline.  Development for
the 2.6.35 merge window went ahead full steam at the same time.

While a fair amount of patches hit the development tree these were
largely cleanups, with the real development activity happening on
the mailing list.  There was another round of patches and following
discussion on the scalable busy extent tracking and delayed logging
features mentioned last month.  They are expected to be merged in
May and queue up for the Linux 2.6.35 window.  Last but not least
April saw a large number of XFS fixes backported to the 2.6.32 and
2.6.33 -stable series.

In user land xfsprogs has seen few but important updates, preparing
for a new release next month.  The xfs_repair tool saw a fix to
correctly enable the lazy superblock counters on an existing
filesystem, and xfs_fsr saw updates to better deal with dynamic
attribute forks.  Last but not a least a port to Debian GNU/kFreeBSD
got merged. The xfstests test suite saw two new test cases and various
smaller fixes.
--
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/