From: Mauricio Faria de Oliveira <mfo@canonical.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: fstests <fstests@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] fstests: overlay: initial support for aufs and
Date: Mon, 17 Feb 2020 12:44:15 -0300 [thread overview]
Message-ID: <CAO9xwp2Z6eF8xnkyh9rsTzCjGJNgZ2ogrLxqzosgjq3YRWeb2w@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxjGdBtzmd=anCbuKo23wMWTu8Ja36-qgGomGy7RSMJ0sg@mail.gmail.com>
On Fri, Feb 14, 2020 at 3:45 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> +CC: <linux-unionfs@vger.kernel.org>
>
> On Fri, Feb 14, 2020 at 5:18 PM Mauricio Faria de Oliveira
> <mfo@canonical.com> wrote:
> >
> > This patchset allows the existing support for overlay to be used with
> > aufs and fuse-overlayfs, so the increase the coverage/test tools that
> > are available for these filesystems.
> >
> > Initial numbers on v5.4-based Ubuntu kernel on Ubuntu Eoan/19.10
> > (fuse-overlay installed from distro package), few tests excluded:
> >
> > OVL_FSTYP=aufs
> > - Ran: 645 tests
> > - Not run: 483 tests
> > - Failures: 22 tests
> >
> > OVL_FSTYP=fuse.fuse-overlayfs
> > - Ran: 530
> > - Not run: 395
> > - Failures: 29
> >
>
> It'd be interesting to know the baseline - what are those numbers for
> OVL_FSTYP=overlay with same kernel?
>
Oh, indeed.
Here's the numbers for the 3 filesystems again (re-runs as I noticed
some tests skipped in fuse-overlayfs previously.)
OVL_FSTYP=overlay (unset/default)
- Ran: 654
- Not run: 391
- Failures: 5
OVL_FSTYP=fuse.fuse-overlayfs
- Ran: 653
- Not run: 472
- Failures: 54
OVL_FSTYP=aufs
- Ran: 645
- Not run: 483
- Failures: 22
BTW, thanks for reviewing/commenting on the individual patches.
I'll review them in more detail, and think I can send out a v3 next week.
cheers,
Mauricio
> Thanks,
> Amir.
>
> > Thanks to Amir Goldstein for review/improvements/suggestions.
> >
> > Changes:
> > - v2:
> > - fix tests/overlay that hardcode the overlay fs type
> > - add support to fuse-overlayfs with +3 other patches
> > - v1:
> > - [PATCH] common/overlay,rc: introduce OVL_ALT_FSTYP for testing aufs
> >
> > Mauricio Faria de Oliveira (5):
> > common/overlay,rc,config: introduce OVL_FSTYP variable and aufs
> > tests/overlay: mount: replace overlay hardcode with OVL_FSTYP variable
> > common/rc: introduce new helper function _fs_type_dev_dir()
> > common/rc: add quirks for fuse-overlayfs device/mount point
> > common/overlay: silence some mount messages for fuse-overlayfs
> >
> > README.overlay | 5 ++++
> > common/config | 2 ++
> > common/overlay | 29 +++++++++++++++++++---
> > common/rc | 61 ++++++++++++++++++++++++++++++++++++++++-------
> > tests/overlay/011 | 2 +-
> > tests/overlay/035 | 2 +-
> > tests/overlay/052 | 4 ++--
> > tests/overlay/053 | 4 ++--
> > tests/overlay/062 | 2 +-
> > 9 files changed, 92 insertions(+), 19 deletions(-)
> >
> > --
> > 2.20.1
> >
--
Mauricio Faria de Oliveira
prev parent reply other threads:[~2020-02-17 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 15:18 [PATCH v2 0/5] fstests: overlay: initial support for aufs and Mauricio Faria de Oliveira
2020-02-14 15:18 ` [PATCH v2 1/5] common/overlay,rc,config: introduce OVL_FSTYP variable and aufs Mauricio Faria de Oliveira
2020-02-14 22:06 ` Amir Goldstein
2020-02-14 15:18 ` [PATCH v2 2/5] tests/overlay: mount: replace overlay hardcode with OVL_FSTYP variable Mauricio Faria de Oliveira
2020-02-14 22:12 ` Amir Goldstein
2020-02-14 15:18 ` [PATCH v2 3/5] common/rc: introduce new helper function _fs_type_dev_dir() Mauricio Faria de Oliveira
2020-02-14 22:20 ` Amir Goldstein
2020-02-14 15:18 ` [PATCH v2 4/5] common/rc: add quirks for fuse-overlayfs device/mount point Mauricio Faria de Oliveira
2020-02-14 22:37 ` Amir Goldstein
2020-02-14 15:18 ` [PATCH v2 5/5] common/overlay: silence some mount messages for fuse-overlayfs Mauricio Faria de Oliveira
2020-02-14 22:51 ` Amir Goldstein
2020-02-14 18:45 ` [PATCH v2 0/5] fstests: overlay: initial support for aufs and Amir Goldstein
2020-02-17 15:44 ` Mauricio Faria de Oliveira [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=CAO9xwp2Z6eF8xnkyh9rsTzCjGJNgZ2ogrLxqzosgjq3YRWeb2w@mail.gmail.com \
--to=mfo@canonical.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
/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).