linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] overlay: test creating lower hardlinks for copied up files
Date: Tue, 31 Oct 2017 11:32:15 +0800	[thread overview]
Message-ID: <20171031033215.GE17339@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxj-AQcW8__3DcL5e+PSejYgW8kP=RD4OOxsD8OGOFZeSg@mail.gmail.com>

On Mon, Oct 30, 2017 at 02:10:52PM +0200, Amir Goldstein wrote:
> On Mon, Oct 30, 2017 at 2:06 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > kernel v4.13 introduced the index=on feature for not breaking hardlinks
> > on copy-up.  With the index feature enabled a regression was introduced -
> > lower files that are hardlined while overlay is offline can result in
> > lookup error after overlay in mounted.
> >
> > The regression was fixed by upstream commit
> >   6eaf011144af ovl: fix EIO from lookup of non-indexed upper
> > that was merged to v4.14-rc7.
> >
> > This test verifies that behavior is sane after creating lower hardlinks
> > for copied up files while overlayfs is offline.
> >
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > ---
> >
> > Eryu,
> >
> > This is a regression test for a fix that was just merged to v4.14-rc7.
> >
> > The test requires and enables index=on, so it would fail on kernels
> > prior to v4.14-rc7 regardless if they are complied with
> > CONFIG_OVERLAY_FS_INDEX=y or not.
> >
> > Amir.
> >
> >  tests/overlay/042     | 137 ++++++++++++++++++++++++++++++++++++++++++++++++++
> >  tests/overlay/042.out |   2 +
> >  tests/overlay/group   |   1 +
> >  3 files changed, 140 insertions(+)
> >  create mode 100755 tests/overlay/042
> >  create mode 100644 tests/overlay/042.out
> >
> > diff --git a/tests/overlay/042 b/tests/overlay/042
> > new file mode 100755
> > index 0000000..29858d6
> > --- /dev/null
> > +++ b/tests/overlay/042
> > @@ -0,0 +1,137 @@
> > +#! /bin/bash
> > +# FS QA Test 042
> > +#
> > +# Test creating lower hardlinks for copied up files.
> > +#
> > +# kernel v4.13 introduced the index=on feature for not breaking
> > +# hardlinks on copy-up. With the index feature enabled a regression was
> > +# introduced - lower files that are hardlined while overlay is offline
> > +# can result in lookup error after overlay in mounted.
> > +# The regression was fixed by upstream commit
> 
> Some indentation fixes I forgot to commit:
> 
> +# kernel v4.13 introduced the index=on feature for not breaking hardlinks
> +# on copy-up.  With the index feature enabled a regression was introduced -
> +# lower files that are hardlined while overlay is offline can result in
> +# lookup error after overlay in mounted.

I've fixed it up on commit, thanks!

Eryu

      reply	other threads:[~2017-10-31  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 12:06 [PATCH] overlay: test creating lower hardlinks for copied up files Amir Goldstein
2017-10-30 12:10 ` Amir Goldstein
2017-10-31  3:32   ` 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=20171031033215.GE17339@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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;
as well as URLs for NNTP newsgroup(s).