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 v3] overlay/016: split into two tests
Date: Sun, 26 Aug 2018 20:39:13 +0800 [thread overview]
Message-ID: <20180826123913.GA3651@desktop> (raw)
In-Reply-To: <CAOQ4uxjaUUMZyfsYs2A=O661XoEq68rktSjFTqLPVZ4V91CCNA@mail.gmail.com>
On Fri, Aug 24, 2018 at 01:51:04PM +0300, Amir Goldstein wrote:
> On Fri, Aug 24, 2018 at 7:38 AM 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 now passes with stacked overlay file operations
> > patch set merged. The second case will still fail.
> >
> > By splitting the two test cases we get one regression test for
> > the common case of ro/rw fd data inconsistecy with pread and
> > one test to track the remaining non-standard behavior of
> > overlayfs w.r.t mmap.
> >
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > ---
> >
> > Eryu,
> >
> > The overlayfs ro/rw fd data inconsistecies patches were
> > finally merged, so we can now merge this test change to
> > reflect new behavior.
> >
> > After this change on current master:
> > - overlay/16 is expected to pass
> > - overlay/61 is expected to fail
> >
> > FYI, overlay/60 (new metacopy feature test) is also expected to
> > run and pass on master.
> >
>
> Eryu,
>
> More FYI from testing overlayfs over ext4/xfs on master:
> - With base fs xfs, swap group tests crash the kernel - sent out a fix
> - With base fs xfs, overlay/019 stress test hits lockdep "circular dependency"
> and "downgrading a read lock" warnings - it seems like a 4.18-rc1 regression
> I will need more time to investigate
> - With base fs ext4, the 6 tests that do "_test_generic_punch -d" fail -
> all expect for generic/009 are regressions from this cycle
>
> The above generic tests failures are the only failures I observed with
> "check -overlay -g quick" apart from test that also fail on base fs
> (e.g. generic/484).
Thanks a lot for the detailed information!
Eryu
next prev parent reply other threads:[~2018-08-26 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 4:40 [PATCH v3] overlay/016: split into two tests Amir Goldstein
2018-08-24 10:51 ` Amir Goldstein
2018-08-26 12:39 ` Eryu Guan [this message]
2018-08-26 14:34 ` 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=20180826123913.GA3651@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