All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Al Viro <viro@zeniv.linux.org.uk>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: unionmount-testsuite: backward compat support for REDIRECT_DIR=n
Date: Tue, 30 May 2017 16:35:48 -0400	[thread overview]
Message-ID: <20170530203548.GA22558@redhat.com> (raw)
In-Reply-To: <CAOQ4uxiEz0mGEQKmQav+g=kLVfq+Ct9GpZvUq7kGvZG7-7gM0A@mail.gmail.com>

On Sun, May 28, 2017 at 05:43:45PM +0300, Amir Goldstein wrote:
> On Tue, Apr 25, 2017 at 5:20 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > On Tue, Apr 25, 2017 at 4:53 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> >> On Tue, Apr 25, 2017 at 04:49:00PM +0300, Amir Goldstein wrote:
> >>> On Tue, Apr 25, 2017 at 4:29 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> ...
> >>> >
> >>> > I will enable it now. I just had an old config and ran into this.
> >>> >
> >>> > But this does raise the question unionmount-testsuite need to be
> >>> > maintained somewhere so that it acts as a baseline to figure out if
> >>> > new patches broke some existing tests.
> >>> >
> >>> > I can go by the tree you are maintaining but currently that's broken too
> >>> > with REDIRECT_DIR=n.
> >>> >
> >>>
> >>> Right.
> >>> I have given some though about what's the best way to handle this.
> >>> Probably need a test flag --noredirect. I'll add this to my TODO...
> >>>
> >>> BTW, I try to keep the branch overlayfs-devel uptodate for testing
> >>> latest features. It could be rebased, but I'll make an effort not to.
> >>> If there is a need for a more stable non-rewindable branch, let me know.
> >>
> >> I think would be good if you maintain "master" branch of your tree up
> >> to date and hopefully that's stable so that later git pull does not talk
> >> about conflicts. We can then use your tree for setting a baseline and
> >> detecting regressions.
> >>
> >> CCing Dave Howells, in case he is interested in continuing to update his
> >> tree as overlayfs kernel development takes place.
> >>
> >
> > OK. declaring branch master on my tree 'ff-only':
> > https://github.com/amir73il/unionmount-testsuite/tree/master
> >
> 
> Vivek,
> 
> I added support for running my maser branch with old kernels
> or with REDIRECT_DIR=n.
> 
> User needs to request backward compat mode explicitly.
> When using new command line arg --xdev,
> dir rename tests that would return EXDEV are skipped.
> 
> User will get a hint to use the new flag when such a test fails, e.g.:
> 
> root@kvm-xfstests:~/unionmount-testsuite# ./run --ov rename-empty-dir
> ***
> *** ./run --ov --ts=0 rename-empty-dir
> ***
> TEST rename-empty-dir.py:10: Rename empty dir and rename back
>  ./run --rename /mnt/a/empty100 /mnt/a/no_dir100
> /mnt/a/empty100: Unexpected error: Invalid cross-device link; Run
> tests with --xdev to skip dir rename tests
> 
> Updated my master branch.
> 
> The new head of the master branch is commit:
> 
>   be7354d Use ./run --ov --xdev for backward compat mode

Ok, thanks Amir.

So --xdev will skip tests which are not supposed to pass without
REDIRECT_DIR=n?

Would be great if we could automate this. That is test which are not valid
with current kernel/overlay configuration are skipped automatically. It
totally up to you. :-)

Vivek

  reply	other threads:[~2017-05-30 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-28 14:43 unionmount-testsuite: backward compat support for REDIRECT_DIR=n Amir Goldstein
2017-05-30 20:35 ` Vivek Goyal [this message]
2017-05-31  7:56   ` Amir Goldstein
2017-05-31 18:53     ` Amir Goldstein

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=20170530203548.GA22558@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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 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.