From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for August 2009
Date: Tue, 8 Sep 2009 22:14:53 -0400 [thread overview]
Message-ID: <20090909021453.GA24173@infradead.org> (raw)
In August the Linux 2.6.31 kernel has still been in the release candidate
stage, but a couple of important XFS fixes made it in time for the release,
including a fix for the inode cache races with NFS workloads that have
plagued us for a long time.
The list saw various patches destined for the Linux 2.6.32 merge window,
including a merge of the fsync and O_SYNC handling code to address various
issues with the latter, a workaround for deficits in the timestamp handling
interface between the VFS and filesystems, a repost of the sync improvements
patch series and various smaller patches.
August also saw the minor 3.0.3 release of xfsprogs which collects smaller
fixes to the various tools and most importantly a fix to allow xfsprogs to
work again on SPARC and other strict alignment handling which regressed a
few releases ago. The xfstests repository saw a few new test cases and a
various small improvements.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-09-09 2:14 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=20090909021453.GA24173@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