From: "zhangyi (F)" <yi.zhang@huawei.com>
To: linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Cc: miklos@szeredi.hu, amir73il@gmail.com, eguan@redhat.com,
yi.zhang@huawei.com, miaoxie@huawei.com, yangerkun@huawei.com
Subject: [xfstests PATCH v5 0/7] overlay: add fsck.overlay basic tests
Date: Tue, 23 Jan 2018 15:34:45 +0800 [thread overview]
Message-ID: <20180123073452.19074-1-yi.zhang@huawei.com> (raw)
Hi All:
Here is the fifth version of test cases for the fsck.overlay[1].
[1] https://github.com/hisilicon/overlayfs-progs
Changes since v4:
- Add _overlay_check_scratch_dirs helper to check optionally dirs
for tests use _require_overlay_scratch_dirs.
- Modify _overlay_check_fs, make sure overlay is not mounted when
checking filesystem.
-----------
Changes since v3:
- Modify minor suggestions in 202.
- Add _require_overlay_scratch_dirs helper.
- Replace _require_scratch helper in test cases that finished with
corrupt filesystem and use optionally test dirs.
Changes since v2:
- Modify some minor suggestions from Amir and Vivek, and simplify code
in all three test cases.
- Fix duplicate redirect xattr test in 202.
- Add impure xattr test case of general merge directory in 'no impure'
parent directory.
- Fix fs check failure in other overlay fs test cases. PS: The
multi-lowers problem in overlay/010 also appears in many other tests,
_require_scratch() will mis-check the pre-defined underlying dirs
(not the real test dirs). I think they also need to be modified as this
patch(06/07) does to check the correct dirs, and I can fix them if you
think necessary.
Changes since v1:
- Fix _check_scratch_fs hook.
- Remove valid/invalid opaque xattr test.
- Add whiteout test cases of valid/invalid whiteouts in opaque/redirect
parent directory.
- Add impure xattr test.
zhangyi (F) (7):
overlay: add filesystem check helper
overlay: add fsck.overlay whiteout test
overlay: add fsck.overlay redirect directory test
overlay: add fsck.overlay impure xattr test
overlay/003: fix fs check failure
overlay: skip check for tests finished with corrupt filesystem
overlay: replace _require_scratch() in optionally dirs cases
common/config | 1 +
common/overlay | 145 +++++++++++++++++++++++++++
common/rc | 4 +-
tests/overlay/003 | 1 -
tests/overlay/005 | 6 +-
tests/overlay/010 | 6 +-
tests/overlay/014 | 10 +-
tests/overlay/019 | 2 +-
tests/overlay/031 | 2 +-
tests/overlay/035 | 6 +-
tests/overlay/036 | 5 +-
tests/overlay/037 | 6 +-
tests/overlay/038 | 10 +-
tests/overlay/041 | 10 +-
tests/overlay/043 | 6 +-
tests/overlay/044 | 6 +-
tests/overlay/201 | 232 +++++++++++++++++++++++++++++++++++++++++++
tests/overlay/201.out | 10 ++
tests/overlay/202 | 269 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/overlay/202.out | 11 +++
tests/overlay/203 | 143 +++++++++++++++++++++++++++
tests/overlay/203.out | 4 +
tests/overlay/group | 3 +
23 files changed, 883 insertions(+), 15 deletions(-)
create mode 100755 tests/overlay/201
create mode 100644 tests/overlay/201.out
create mode 100755 tests/overlay/202
create mode 100644 tests/overlay/202.out
create mode 100755 tests/overlay/203
create mode 100644 tests/overlay/203.out
--
2.5.0
next reply other threads:[~2018-01-23 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 7:34 zhangyi (F) [this message]
2018-01-23 7:34 ` [xfstests PATCH v5 1/7] overlay: add filesystem check helper zhangyi (F)
2018-01-23 9:16 ` Amir Goldstein
2018-01-23 11:10 ` zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 2/7] overlay: add fsck.overlay whiteout test zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 3/7] overlay: add fsck.overlay redirect directory test zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 4/7] overlay: add fsck.overlay impure xattr test zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 5/7] overlay/003: fix fs check failure zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 6/7] overlay: skip check for tests finished with corrupt filesystem zhangyi (F)
2018-01-23 7:34 ` [xfstests PATCH v5 7/7] overlay: correct scratch dirs check zhangyi (F)
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=20180123073452.19074-1-yi.zhang@huawei.com \
--to=yi.zhang@huawei.com \
--cc=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=miklos@szeredi.hu \
--cc=yangerkun@huawei.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