From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>, ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 3/3] xfstests: fallocate + read/write tests, ext4 regression tests
Date: Sat, 20 Jun 2009 13:59:53 -0400 [thread overview]
Message-ID: <20090620175953.GC3984@infradead.org> (raw)
In-Reply-To: <4A370DD2.6080204@sandeen.net>
On Mon, Jun 15, 2009 at 10:13:22PM -0500, Eric Sandeen wrote:
> New test to test basic mixed fallocate + read & write,
> includes a couple regression tests for bugs that ext4
> hit. Uses xfs_io to generate fallocate calls, so requires
> git xfsprogs and very recent glibc at this point.
Looks good to me, and again does the correct notrun for my 32-bit
VM. Guess I need to do the raw syscall wireup i xfsprogs eventually..
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2009-06-20 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 3:13 [PATCH 3/3] xfstests: fallocate + read/write tests, ext4 regression tests Eric Sandeen
2009-06-20 17:59 ` Christoph Hellwig [this message]
2009-06-20 21:00 ` Eric Sandeen
2009-06-21 19:17 ` Christoph Hellwig
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=20090620175953.GC3984@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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;
as well as URLs for NNTP newsgroup(s).