From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 2/8] fstests: _cleanup overrides are messy
Date: Tue, 24 May 2022 17:34:05 +1000 [thread overview]
Message-ID: <20220524073411.1943480-3-david@fromorbit.com> (raw)
In-Reply-To: <20220524073411.1943480-1-david@fromorbit.com>
From: Dave Chinner <dchinner@redhat.com>
Most _cleanup() function overrides look like:
_cleanup()
{
# do something test specific
cd /
rm -rf $tmp.*
}
But they often get the last two lines either wrong or omit them.
These are the lines the common/preamble::_cleanup() define.
The problem here is that we are just overriding the generic _cleanup
function by redeclaring it after calling _begin_fstest. What we
should be doing is registering a new local cleanup function that
calls the generic cleanup function when we have finished the local
cleanup. i.e.:
_local_cleanup()
{
# do something test specific
_cleanup
}
Make _register_cleanup() function to cancel the existing
cleanup trap and register the new trap function so that local
cleanups can be done cleanly.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
---
common/preamble | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/common/preamble b/common/preamble
index e60cd949..7aa55dc6 100644
--- a/common/preamble
+++ b/common/preamble
@@ -4,7 +4,9 @@
# Boilerplate fstests functionality
-# Standard cleanup function. Individual tests can override this.
+# Standard cleanup function. If individual tests register their own cleanup
+# function, they need to call this from within their own cleanup function once
+# the test has finished cleaning up it's own state.
_cleanup()
{
cd /
@@ -19,6 +21,9 @@ _register_cleanup()
local cleanup="$1"
shift
+ # clear out existing traps first
+ trap - EXIT HUP INT QUIT TERM $*
+
test -n "$cleanup" && cleanup="${cleanup}; "
trap "${cleanup}exit \$status" EXIT HUP INT QUIT TERM $*
}
--
2.35.1
next prev parent reply other threads:[~2022-05-24 7:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 7:34 [RFC PATCH 0/8] fstests: _cleanup() overrides are a mess Dave Chinner
2022-05-24 7:34 ` [PATCH 1/8] generic/038: kill background threads on interrupt Dave Chinner
2022-05-24 9:41 ` Amir Goldstein
2022-05-24 12:10 ` Dave Chinner
2022-05-24 12:30 ` Amir Goldstein
2022-05-24 7:34 ` Dave Chinner [this message]
2022-05-24 16:16 ` [PATCH 2/8] fstests: _cleanup overrides are messy Amir Goldstein
2022-05-24 7:34 ` [PATCH 3/8] xfs/*: clean up _cleanup override Dave Chinner
2022-05-24 10:42 ` Amir Goldstein
2022-05-24 12:27 ` Dave Chinner
2022-05-24 12:55 ` Amir Goldstein
2022-05-24 13:24 ` Dave Chinner
2022-05-24 14:17 ` Amir Goldstein
2022-05-24 16:32 ` Zorro Lang
2022-05-24 23:34 ` Dave Chinner
2022-05-25 2:54 ` Amir Goldstein
2022-05-24 17:13 ` Zorro Lang
2022-05-26 15:04 ` Zorro Lang
2022-05-26 23:39 ` Dave Chinner
2022-05-24 7:34 ` [PATCH 4/8] fstests: define a common _dump_cleanup function Dave Chinner
2022-05-24 9:04 ` Amir Goldstein
2022-05-24 9:52 ` Dave Chinner
2022-05-24 9:59 ` Amir Goldstein
2022-05-24 7:34 ` [PATCH 5/8] fstests: use a common fsstress cleanup function Dave Chinner
2022-05-24 12:25 ` Amir Goldstein
2022-05-24 7:34 ` [PATCH 6/8] fstests: consolidate no cleanup test setup Dave Chinner
2022-05-24 12:22 ` Amir Goldstein
2022-05-24 13:07 ` Dave Chinner
2022-05-24 7:34 ` [PATCH 7/8] fstests: Set up BUS trap for tests by default Dave Chinner
2022-05-24 8:48 ` Amir Goldstein
2022-05-24 7:34 ` [PATCH 8/8] fstests: cleanup _cleanup usage in shared Dave Chinner
2022-05-24 10:49 ` Amir Goldstein
2022-05-24 11:11 ` Amir Goldstein
2022-05-24 8:29 ` [RFC PATCH 0/8] fstests: _cleanup() overrides are a mess Amir Goldstein
2022-05-24 9:57 ` Dave Chinner
2022-05-24 10:01 ` Amir Goldstein
2022-05-24 10:13 ` Dave Chinner
2022-05-24 12:14 ` Amir Goldstein
2022-05-24 12:28 ` Dave Chinner
2022-05-24 12:34 ` 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=20220524073411.1943480-3-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
/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