From: Eryu Guan <guaneryu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Vivek Goyal <vgoyal@redhat.com>,
overlayfs <linux-unionfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] overlay/016: split into two tests
Date: Thu, 7 Jun 2018 13:34:56 +0800 [thread overview]
Message-ID: <20180607053456.GB2861@desktop> (raw)
In-Reply-To: <CAOQ4uxiw12OvPxtyzZgyoKNKW69J0=VTRTM3CMa4mxBQLj5c3g@mail.gmail.com>
On Tue, Jun 05, 2018 at 03:09:59PM +0300, Amir Goldstein wrote:
> On Sat, Jun 2, 2018 at 9:52 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > overlay/016 tests two cases of ro/rw fd data inconsistecies -
> > one using pread and one using mmap read (i.e. mread).
> >
> > The first case will pass as soon as stacked overlay operations
> > patch set is merged. The second case requires enabling a new opt-in
> > feature "copy_up_shared" in order to pass.
> >
> > Instead of changing the entire test from fail to notrun, split
> > the two cases into two tests and require the new feature only
> > for the new test.
> >
> > This way, the new test will change from notrun to pass with
> > stacked overlay operations and the old test will change from
> > fail to pass.
> >
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > ---
>
> Eryu,
>
> Please hold back on this patch - there seems to be a push back
> on the "copy_up_shared" feature.
> It may end up making sense to do the split anyway because
> case #1 may be resolved in this merge cycle and case #2 only
> later on, but let's wait to see what gets merged first and then decide.
Thanks for the heads-up! I removed the patch from my to-review queue,
please re-submit when the decision is made.
>
> No problem with merging the cleanup patch
> "overlay: nicer report when features are not supported"
OK.
Thanks,
Eryu
prev parent reply other threads:[~2018-06-07 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 18:52 [PATCH v2 2/2] overlay/016: split into two tests Amir Goldstein
2018-06-04 18:49 ` Vivek Goyal
2018-06-05 12:09 ` Amir Goldstein
2018-06-07 5:34 ` 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=20180607053456.GB2861@desktop \
--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;
as well as URLs for NNTP newsgroup(s).