From: Amir Goldstein <amir73il@gmail.com>
To: Mauricio Faria de Oliveira <mfo@canonical.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: Fri, 14 Feb 2020 20:45:13 +0200 [thread overview]
Message-ID: <CAOQ4uxjGdBtzmd=anCbuKo23wMWTu8Ja36-qgGomGy7RSMJ0sg@mail.gmail.com> (raw)
In-Reply-To: <20200214151848.8328-1-mfo@canonical.com>
+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?
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
>
next parent reply other threads:[~2020-02-14 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200214151848.8328-1-mfo@canonical.com>
2020-02-14 18:45 ` Amir Goldstein [this message]
2020-02-17 15:44 ` [PATCH v2 0/5] fstests: overlay: initial support for aufs and Mauricio Faria de Oliveira
[not found] ` <20200214151848.8328-2-mfo@canonical.com>
2020-02-14 22:06 ` [PATCH v2 1/5] common/overlay,rc,config: introduce OVL_FSTYP variable and aufs Amir Goldstein
[not found] ` <20200214151848.8328-4-mfo@canonical.com>
2020-02-14 22:20 ` [PATCH v2 3/5] common/rc: introduce new helper function _fs_type_dev_dir() Amir Goldstein
[not found] ` <20200214151848.8328-5-mfo@canonical.com>
2020-02-14 22:37 ` [PATCH v2 4/5] common/rc: add quirks for fuse-overlayfs device/mount point Amir Goldstein
[not found] ` <20200214151848.8328-6-mfo@canonical.com>
2020-02-14 22:51 ` [PATCH v2 5/5] common/overlay: silence some mount messages for fuse-overlayfs 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='CAOQ4uxjGdBtzmd=anCbuKo23wMWTu8Ja36-qgGomGy7RSMJ0sg@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mfo@canonical.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).