From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: allow more xfs_io tests to be generic
Date: Mon, 8 Jun 2009 19:25:59 -0400 [thread overview]
Message-ID: <20090608232559.GA28568@infradead.org> (raw)
In-Reply-To: <4A2D4F51.5050906@redhat.com>
On Mon, Jun 08, 2009 at 12:50:09PM -0500, Eric Sandeen wrote:
> What do folks think of this? These tests just do generic
> reads & writes with xfs_io; if we add a "-F" they will run
> on other filesystems.
Looks good to me. Btw, I really wonder if we want to keep the -F
flag to xfs_io. Seems rather pointless to restrict
perfectly normal I/O to a single filesystem type. And even for XFS
specific ioctls we'd get a good enough error code back to handle it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-08 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 17:50 [PATCH] xfstests: allow more xfs_io tests to be generic Eric Sandeen
2009-06-08 23:25 ` Christoph Hellwig [this message]
2009-06-09 0:49 ` Eric Sandeen
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=20090608232559.GA28568@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@redhat.com \
--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