From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Dushan Tcholich <dusanc@gmail.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/038: require fallocate support and test for trim support
Date: Tue, 16 Dec 2014 09:07:04 +1100 [thread overview]
Message-ID: <20141215220704.GA2152@dastard> (raw)
In-Reply-To: <20141215214510.GL17575@thunk.org>
On Mon, Dec 15, 2014 at 04:45:10PM -0500, Theodore Ts'o wrote:
> On Tue, Dec 16, 2014 at 07:49:15AM +1100, Dave Chinner wrote:
> > On Mon, Dec 15, 2014 at 11:26:35PM +0100, Dushan Tcholich wrote:
> > > Add tests for allocate support and test if TRIM really works on tested
> > > partition.
> > >
> > > Signed-off-by: Dushan Tcholich <dusanc@gmail.com>
> > >
> > > --- xfstests.orig/tests/generic/038 2014-12-14 15:18:00.000000000 +0100
> > > +++ xfstests/tests/generic/038 2014-12-15 23:21:11.000000000 +0100
> > > @@ -70,6 +70,10 @@
> > > _supported_os Linux
> > > _require_scratch
> > > _require_fstrim
> > > +_require_xfs_io_command "falloc"
> > > +_require_xfs_io_command "truncate"
> >
> > No need to test for the truncate command as it's supported in all
> > versions of xfs_io people use. falloc, OTOH, isn't supported on oler
> > distros that people still need to run QA on, and hence that check is
> > required....
>
> I've also been using '_require_xfs_io_command "falloc"' to test
> whether the file system supports fallocate(2). So for example, in the
> patch that I sent out today, I'm checking not just whether xfs_io
> supports "falloc", but whether the file system under test (at least
> with a specific configuration, such as ext4 in ext3 compatibility
> mode) supports fallocate(2). Do you consider that a valid thing to
> do?
Yes, that's it's intent. From the 2009 patch that introduced
checks for fallocate support:
+# check that xfs_io, glibc, kernel, and filesystem all (!) support
+# fallocate
+#
+_require_xfs_io_falloc()
i.e. the one function checks the entire stack for fallocate support.
That's not going to change.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2014-12-15 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 22:26 [PATCH] generic/038: require fallocate support and test for trim support Dushan Tcholich
2014-12-15 20:49 ` Dave Chinner
2014-12-15 21:45 ` Theodore Ts'o
2014-12-15 22:07 ` Dave Chinner [this message]
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=20141215220704.GA2152@dastard \
--to=david@fromorbit.com \
--cc=dusanc@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.