From: "zhangyi (F)" <yi.zhang@huawei.com>
To: fstests@vger.kernel.org, amir73il@gmail.com
Cc: guaneryu@gmail.com, miklos@szeredi.hu, yi.zhang@huawei.com,
miaoxie@huawei.com
Subject: [PATCH v2 0/4] overlay: enhance fsck.overlay test cases
Date: Tue, 16 Oct 2018 15:45:55 +0800 [thread overview]
Message-ID: <20181016074559.24728-1-yi.zhang@huawei.com> (raw)
Hi all,
These are the second version of fsck.overlay[1] program related patch set
(the first one was posted about two mounths ago[2], sorry for the late).
I have fix all comments as Amir suggested and looks fine after test.
The first two patches correct the exit code and fix the tests failure
with master branch of fsck.overlay, and the last two patches were just
want to test stability and exception handling processes.
Hi Amir,
Patch 1 and 2 will fix the test failure you mentioned yesterday when you
run -g overlay/fsck with fsck.overlay's master branch. I am very grateful
if you can give a review.
Thanks,
Yi.
Changes from v1:
- split patch 2 from patch 1 for readable.
- move exit code definitions from common/config to common/overlay.
- factor out a common function _run_check_fsck() to fsck and check
return value.
- fix some mistakes in patch 3 and 4.
[1] https://github.com/hisilicon/overlayfs-progs/commits/master
[2] https://www.spinics.net/lists/fstests/msg10267.html
zhangyi (F) (4):
overlay: correct fsck.overlay exit code
overlay: fix exit code for some fsck.overlay valid cases
overlay: add fsck.overlay stress test
overlay: add fsck.overlay exception tests
common/overlay | 37 ++++++++-
tests/overlay/045 | 46 ++++++-----
tests/overlay/046 | 49 ++++++------
tests/overlay/056 | 9 +--
tests/overlay/062 | 84 +++++++++++++++++++
tests/overlay/062.out | 2 +
tests/overlay/063 | 217 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/overlay/063.out | 10 +++
tests/overlay/group | 2 +
9 files changed, 403 insertions(+), 53 deletions(-)
create mode 100755 tests/overlay/062
create mode 100644 tests/overlay/062.out
create mode 100755 tests/overlay/063
create mode 100644 tests/overlay/063.out
--
2.5.0
next reply other threads:[~2018-10-16 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 7:45 zhangyi (F) [this message]
2018-10-16 7:45 ` [PATCH v2 1/4] overlay: correct fsck.overlay exit code zhangyi (F)
2018-10-16 9:45 ` Amir Goldstein
2018-10-18 2:37 ` zhangyi (F)
2018-10-18 4:37 ` Amir Goldstein
2018-10-18 16:22 ` zhangyi
2018-10-18 4:54 ` Amir Goldstein
2018-10-16 7:45 ` [PATCH v2 2/4] overlay: fix exit code for some fsck.overlay valid cases zhangyi (F)
2018-10-16 9:26 ` Amir Goldstein
2018-10-18 3:42 ` zhangyi (F)
2018-10-18 4:44 ` Amir Goldstein
2018-10-19 12:36 ` zhangyi (F)
2018-10-19 14:00 ` Amir Goldstein
2018-10-16 7:45 ` [PATCH v2 3/4] overlay: add fsck.overlay stress test zhangyi (F)
2018-10-16 10:07 ` Amir Goldstein
2018-10-18 3:48 ` zhangyi (F)
2018-10-16 7:45 ` [PATCH v2 4/4] overlay: add fsck.overlay exception tests zhangyi (F)
2018-10-16 13:29 ` Amir Goldstein
2018-10-16 9:27 ` [PATCH v2 0/4] overlay: enhance fsck.overlay test cases Amir Goldstein
2018-10-16 12:39 ` Amir Goldstein
2018-10-18 3:50 ` 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=20181016074559.24728-1-yi.zhang@huawei.com \
--to=yi.zhang@huawei.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=miaoxie@huawei.com \
--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