From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for June 2009
Date: Wed, 1 Jul 2009 10:56:20 -0400 [thread overview]
Message-ID: <20090701145620.GA13061@infradead.org> (raw)
On June 9th we finally saw the release of Linux 2.6.30. For XFS
this release mostly contains the improved ENOSPC handling, but also
various smaller bugfixes and lots of cleanups. The code size of XFS
decreased again by 500 lines of code in this release.
The Linux 2.6.31 merge opened in the mid of the month and some big XFS
changes have been pushed: A removal of the quotaops
infrastructure which simplifies the quota implementation, the switch
from XFS's own Posix ACL implementation to the generic one shared
by various other filesystems which also supports in-memory caching of
ACLs and another incremental refactoring of the sync code.
A patch to better track dirty inodes and work around issues in the
way the VFS updates the access time stamp on inodes has been reposted
and discussed. Another patch to converting the existing XFS tracing
infrastructure to use the ftrace even tracer has been posted.
On the userspace side there have been a few updates to xfsprogs, including
some repair fixes and a new fallocate command for xfs_io. There were
major updates for xfstests: The existing aio-dio-regress testsuite has
been merged into xfstests, and various changes went into the tree to make
xfstests better suitable for use with other filesystems.
The attr and acl projects which have been traditionally been hosted
as part of the XFS userspace utilities have now been split into a separate
project maintained by Andreas Gruenbacher, who has been doing most of
the work on it, and moved to the Savannah hosting platform.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-07-01 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090701145620.GA13061@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox