From: Dave Chinner <david@fromorbit.com>
To: David Howells <dhowells@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@infradead.org, akpm@linux-foundation.org, apw@canonical.com,
nbd@openwrt.org, neilb@suse.de, jordipujolp@gmail.com,
ezk@fsl.cs.sunysb.edu, sedat.dilek@gmail.com,
hooanon05@yahoo.co.jp, mszeredi@suse.cz, fstests@vger.kernel.org
Subject: Re: Unionmount and overlayfs testsuite
Date: Fri, 30 May 2014 09:21:14 +1000 [thread overview]
Message-ID: <20140529232114.GJ6677@dastard> (raw)
In-Reply-To: <28592.1401382081@warthog.procyon.org.uk>
[cc fstests@vger.kernel.org]
On Thu, May 29, 2014 at 05:48:01PM +0100, David Howells wrote:
>
> http://git.infradead.org/users/dhowells/unionmount-testsuite.git
>
> Check it out and read the README file as to how to drive it. Sorry, it's a
> bit crude. I may rewrite it in python or perl at some point.
>
> Make sure you turn on CONFIG_LOCKDEP before running it - you don't want to
> miss any locking conflicts!
>
> Further tests would be appreciated. There are no rename tests, for instance.
Rather than keeping this a standalone test suite that nobody really
knows about or runs regularly, perhaps it might be an idea to push
this toward inclusion in xfstests? We have filesystem specific test
sections that would suit this, and the test structure is actually
not all that different to what xfstests uses...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
parent reply other threads:[~2014-05-29 23:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <28592.1401382081@warthog.procyon.org.uk>]
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=20140529232114.GJ6677@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dhowells@redhat.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=jordipujolp@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=nbd@openwrt.org \
--cc=neilb@suse.de \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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