From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for July 2009
Date: Mon, 3 Aug 2009 17:44:45 -0400 [thread overview]
Message-ID: <20090803214445.GA3167@infradead.org> (raw)
As a traditional summer vacation month July has not seen a lot of XFS
activity. The mainline 2.6.31 kernel made it to the 5th release candidate
but besides a few kernel-wide patches touching XFS the only activity were
two small patches fixing a bug in FIEMAP and working around writeback
performance problems in the VM.
A few more patches were posted to the list but haven't been merged yet.
Two big patch series deal with theoretically possible deadlocks due to
locks taken in reclaim contexts, which are now detected by lockdep.
The pace on the userspace side has been slow. There have been a couple
of fixes to xfs_repair and xfs_db, and xfstests grew a few more testcases.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-08-03 21:43 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=20090803214445.GA3167@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