From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: zhangyi <yi.zhang@huawei.com>, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH v3 0/4] Misc. fsck.overlay test fixes
Date: Tue, 28 May 2019 18:17:19 +0300 [thread overview]
Message-ID: <20190528151723.12525-1-amir73il@gmail.com> (raw)
Eryu,
This is a re-post for zhangyi's fsck.overlay test fixes from
October [1]. Based on my own code review of those patches, I have
made some minor modifications and added some more fixes.
I have been carrying the two patches by zhangyi in my dev branch
for a while. Without them running overlay tests with fsck.overlay
installed is failing some tests.
Zhangyi,
Please review my changes, some based on your suggestions.
Feel free to re-post "fsck.overlay stress test" and
"fsck.overlay exception tests". My goal with this posting
was just to fix failures of existing tests when fsck.overlay
is installed.
Thanks,
Amir.
Changes from v2:
- Dropped patches of new tests
- Move fsck exit code constants to common/config
- Fix _repair_scratch_fs
[1] https://marc.info/?l=fstests&m=153967515805435&w=2
Amir Goldstein (2):
fstests: define constants for fsck exit codes
overlay: fix _repair_scratch_fs
zhangyi (F) (2):
overlay: correct fsck.overlay exit code
overlay: fix exit code for some fsck.overlay valid cases
common/config | 11 +++++++++++
common/overlay | 36 ++++++++++++++++++++++++++++++++++
common/rc | 15 ++++++++++++---
tests/overlay/045 | 46 ++++++++++++++++++++++++--------------------
tests/overlay/046 | 49 ++++++++++++++++++++++++-----------------------
tests/overlay/056 | 9 +++------
6 files changed, 112 insertions(+), 54 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-28 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:17 Amir Goldstein [this message]
2019-05-28 15:17 ` [PATCH v3 1/4] fstests: define constants for fsck exit codes Amir Goldstein
2019-05-29 15:57 ` zhangyi (F)
2019-05-28 15:17 ` [PATCH v3 2/4] overlay: fix _repair_scratch_fs Amir Goldstein
2019-05-29 16:10 ` zhangyi (F)
2019-05-28 15:17 ` [PATCH v3 3/4] overlay: correct fsck.overlay exit code Amir Goldstein
2019-05-29 16:13 ` zhangyi (F)
2019-06-02 7:26 ` Eryu Guan
2019-06-02 8:07 ` Amir Goldstein
2019-05-28 15:17 ` [PATCH v3 4/4] overlay: fix exit code for some fsck.overlay valid cases 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=20190528151723.12525-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=yi.zhang@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