From: Amir Goldstein <amir73il@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: "Darrick J . Wong" <darrick.wong@oracle.com>,
Dave Chinner <david@fromorbit.com>,
fstests@vger.kernel.org
Subject: [PATCH 0/4] aborted fstests may leave frozen fs behind
Date: Sun, 19 Jun 2022 16:46:53 +0300 [thread overview]
Message-ID: <20220619134657.1846292-1-amir73il@gmail.com> (raw)
Zorro,
I was analyzing a flakey test failure of xfs/517 and
fell down a rabbit hole of frzon fs cleanups.
Patch 4 fixes the false positive I was running into occasionnaly
in cases where xfs/517 was completed successfully.
While testing, I found out that if I interrupt the run of xfs/517
this often leaves the fs frozen. So I did an audit of the tests that
freeze the fs and found that very few of them unfreeze fs on interrupt.
This is an attempt to provide a robust solution that minimizes the
risks of that happenning.
I tested that all the tests in the 'freeze' group that I modified
run to completion.
I did not try to interrupt all the rest of the tests, because
interrupting a test at exact time that it is frozen is quite hard.
I did test that interrupting xfs/517 several times did not leave the fs
frozen. Before the changes, it was rather easy to get it to leave a
frozen fs behind, because the freeze_loop() keeps the fs frozon around
half of the time that the test is running.
As far as I can tell, this series is orthogonal to Dave's _cleanup()
work [1]. It adds missing cleanups to tests (e.g. xfs/422) that could
later make use of the common cleanup helpers (i.e. _fsstress_cleanup).
However, the common _fsstress_cleanup() helper will need to kill without
waiting. To my understand, Dave was also against waiting in the cleanup
helper.
Thanks,
Amir.
[1] https://lore.kernel.org/fstests/20220524073411.1943480-1-david@fromorbit.com/
Amir Goldstein (4):
fstests: add missing _require_freeze() to tests
fstests: make sure to unfreeze test and scratch mounts
xfs/{422,517}: add missing killall to _cleanup()
xfs/{422,517}: fix false positive failure
check | 14 ++++++++------
common/rc | 5 +++--
tests/generic/390 | 2 --
tests/xfs/011 | 2 --
tests/xfs/119 | 1 +
tests/xfs/318 | 3 ++-
tests/xfs/325 | 3 ++-
tests/xfs/422 | 16 ++++++++++++++--
tests/xfs/438 | 2 +-
tests/xfs/517 | 8 ++++++--
10 files changed, 37 insertions(+), 19 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-19 13:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 13:46 Amir Goldstein [this message]
2022-06-19 13:46 ` [PATCH 1/4] fstests: add missing _require_freeze() to tests Amir Goldstein
2022-06-23 18:00 ` Darrick J. Wong
2022-06-24 4:05 ` Amir Goldstein
2022-06-24 6:27 ` Zorro Lang
2022-06-19 13:46 ` [PATCH 2/4] fstests: make sure to unfreeze test and scratch mounts Amir Goldstein
2022-06-20 11:17 ` Zorro Lang
2022-06-20 12:13 ` Amir Goldstein
2022-06-20 14:21 ` Zorro Lang
2022-06-20 15:08 ` Amir Goldstein
2022-06-20 22:34 ` Dave Chinner
2022-06-21 2:53 ` Amir Goldstein
2022-06-20 22:06 ` Dave Chinner
2022-06-21 2:57 ` Amir Goldstein
2022-06-19 13:46 ` [PATCH 3/4] xfs/{422,517}: add missing killall to _cleanup() Amir Goldstein
2022-06-21 4:02 ` Amir Goldstein
2022-06-23 18:04 ` Darrick J. Wong
2022-06-24 4:36 ` Amir Goldstein
2022-06-24 6:31 ` Zorro Lang
2022-06-24 6:41 ` Amir Goldstein
2022-06-24 15:09 ` Zorro Lang
2022-06-24 4:49 ` Delegating fstests maintenance work (Was: Re: [PATCH 3/4] xfs/{422,517}: add missing killall to _cleanup()) Amir Goldstein
2022-06-25 3:11 ` Darrick J. Wong
2022-06-19 13:46 ` [PATCH 4/4] xfs/{422,517}: fix false positive failure 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=20220619134657.1846292-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.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