From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/2] Fix failing overlay nonsamefs fstests
Date: Wed, 18 Apr 2018 17:16:56 +0300 [thread overview]
Message-ID: <1524061018-20413-1-git-send-email-amir73il@gmail.com> (raw)
Eryu,
The modified 3 tests were introduced to track a non-standard
behavior of overlayfs w.r.t. inode numbers with nonsamefs
configuration.
This behavior cannot be fixed with all underlying filesystems
unless user opts-in for the xino feature.
xino feature was introduced in kernel v4.17-rc1. This patch
set converts the tests to notrun instead of failing on old kernels
and opts-in for xino with new kernels.
FYI, Miklos has a patch set in review to fix the last of the
non-standard behavior tracking test that is still failing (overlay/016).
After that patch set is merged, all overlay tests will be expected to
pass on master - new era ;-)
Thanks,
Amir.
Amir Goldstein (2):
common/rc: factor out _require_scratch_fs_option
overlay/04{1,3,4}: enable xino feature
common/rc | 29 ++++++++++++++++++++++-------
tests/overlay/041 | 15 +++++++++++----
tests/overlay/043 | 13 ++++++++++---
tests/overlay/044 | 15 +++++++++++----
4 files changed, 54 insertions(+), 18 deletions(-)
--
2.7.4
next reply other threads:[~2018-04-18 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 14:16 Amir Goldstein [this message]
2018-04-18 14:16 ` [PATCH 1/2] common/rc: factor out _require_scratch_fs_option Amir Goldstein
2018-04-18 14:16 ` [PATCH 2/2] overlay/04{1,3,4}: enable xino feature Amir Goldstein
2018-04-25 5:48 ` Eryu Guan
2018-04-25 15:32 ` Amir Goldstein
2018-04-18 14:23 ` [PATCH 0/2] Fix failing overlay nonsamefs fstests Miklos Szeredi
2018-04-18 14:30 ` Amir Goldstein
2018-04-23 13:37 ` Miklos Szeredi
2018-04-23 14:50 ` Amir Goldstein
2018-04-23 15:12 ` Miklos Szeredi
2018-04-23 15:57 ` Amir Goldstein
2018-04-23 19:05 ` Miklos Szeredi
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=1524061018-20413-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=eguan@redhat.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