From: Eryu Guan <guaneryu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
fstests <fstests@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH V3] xfstest: overlay: Absolute redirect should be followed even if ancestor is opaque
Date: Fri, 16 Mar 2018 14:18:56 +0800 [thread overview]
Message-ID: <20180316061856.GP30836@localhost.localdomain> (raw)
In-Reply-To: <CAOQ4uximE5LCYk4OGtOoY2VDOPSH+ym7aVEAoEgWGa+u79FOvQ@mail.gmail.com>
On Fri, Mar 16, 2018 at 07:58:35AM +0200, Amir Goldstein wrote:
> On Fri, Mar 16, 2018 at 4:55 AM, Eryu Guan <guaneryu@gmail.com> wrote:
> > On Fri, Mar 16, 2018 at 10:53:20AM +0800, Eryu Guan wrote:
> >
> >> > +# Create opaque parent with absolute redirect child in middle layer
> >> > +mkdir $SCRATCH_MNT/pure
> >> > +mv $SCRATCH_MNT/origin $SCRATCH_MNT/pure/redirect
> >> > +$UMOUNT_PROG $SCRATCH_MNT
> >> > +_overlay_scratch_mount_dirs $lowerdir2:$lowerdir $upperdir $workdir -o redirect_dir=on
> >> > +mv $SCRATCH_MNT/pure/redirect $SCRATCH_MNT/redirect
> >>
> >> I think we'd better do a "ls $SCRATCH_MNT/redirect/" here too, right
> >> after the rename and before mount cycle, to make sure 'foo' is there as
> >> well. I can add it on commit (and change the .out file too) if this
> >> change looks OK to you.
> >
>
> OK, but...
>
> > Something like this:
> >
> > git a/tests/overlay/057 b/tests/overlay/057
> > index 10b46bfa8cff..d54024e98bcd 100644
> > --- a/tests/overlay/057
> > +++ b/tests/overlay/057
> > @@ -86,6 +86,8 @@ mv $SCRATCH_MNT/origin $SCRATCH_MNT/pure/redirect
> > $UMOUNT_PROG $SCRATCH_MNT
> > _overlay_scratch_mount_dirs $lowerdir2:$lowerdir $upperdir $workdir -o redirect_dir=on
> > mv $SCRATCH_MNT/pure/redirect $SCRATCH_MNT/redirect
> > +# Verify that redirects are followed
>
> The wording here is not technically accurate.
> "redirect" are "followed" on lookup and there is no lookup here
> (dentry is already in cache). It would be more accurate to say
> some thing like "List content of renamed merge dir before mount cycle"
> and then maybe to use the same language, "Verify that redirects are
> followed by listing content of renamed merge dir after after cycle".
I'll update as suggested. Thanks!
Eryu
prev parent reply other threads:[~2018-03-16 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 13:16 [PATCH V3] xfstest: overlay: Absolute redirect should be followed even if ancestor is opaque Vivek Goyal
2018-03-14 20:19 ` Amir Goldstein
2018-03-16 2:53 ` Eryu Guan
2018-03-16 2:55 ` Eryu Guan
2018-03-16 5:58 ` Amir Goldstein
2018-03-16 6:18 ` Eryu Guan [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=20180316061856.GP30836@localhost.localdomain \
--to=guaneryu@gmail.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.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