From: Eric Sandeen <sandeen@sandeen.net>
To: fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] fstests: Add overlayfs support
Date: Fri, 20 Mar 2015 13:57:49 -0500 [thread overview]
Message-ID: <550C6DAD.4060602@sandeen.net> (raw)
In-Reply-To: <550C4951.1030804@sandeen.net>
On 3/20/15 11:22 AM, Eric Sandeen wrote:
> If OVERLAYFS=1 is set, then every time we mount the scratch or
> test device, set up overlayfs directories under it, and switch
> the directory under test to the upper directory.
>
> This doesn't specifically or directly test overlayfs, it simply
> runs the existing tests over it. As such, a few tests fail,
> and may be expected to fail due to overlayfs limitations and
> caveats. I haven't sorted through the results yet.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Zach has almost convinced me that this is the wrong approach and/or
not worth doing, or at least not merging.
Many of the failures are as a result of this being tacked on, and
several tests wouldn't be expected to work at all.
So I dunno. What do people think; it's at least interesting on the
side, to see what falls off.
Good news is, no oopses yet! :)
-Eric
next prev parent reply other threads:[~2015-03-20 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 16:11 [PATCH 0/2] fstests: rudimentary overlayfs testing Eric Sandeen
2015-03-20 16:13 ` [PATCH 1/2] fstests: use mount/umount helpers everywhere Eric Sandeen
2015-03-20 18:56 ` Zach Brown
2015-03-20 18:59 ` Eric Sandeen
2015-03-20 20:01 ` Eric Sandeen
2015-03-20 21:01 ` Zach Brown
2015-03-20 16:22 ` [PATCH 2/2] fstests: Add overlayfs support Eric Sandeen
2015-03-20 18:57 ` Eric Sandeen [this message]
2015-04-02 14:41 ` Jan Tulak
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=550C6DAD.4060602@sandeen.net \
--to=sandeen@sandeen.net \
--cc=fstests@vger.kernel.org \
/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