From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com
Cc: Allison Henderson <allison.henderson@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCH 1/1] generic/561: hide assertions when duperemove is killed
Date: Mon, 19 Jul 2021 18:08:29 -0700 [thread overview]
Message-ID: <162674330933.2650745.11380233368495712613.stgit@magnolia> (raw)
In-Reply-To: <162674330387.2650745.4586773764795034384.stgit@magnolia>
From: Darrick J. Wong <djwong@kernel.org>
Use some bash redirection trickery to capture in $seqres.full all of
bash's warnings about duperemove being killed due to assertions
triggering.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
---
tests/generic/561 | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/tests/generic/561 b/tests/generic/561
index bfd4443d..44f07802 100755
--- a/tests/generic/561
+++ b/tests/generic/561
@@ -62,8 +62,13 @@ dupe_run=$TEST_DIR/${seq}-running
touch $dupe_run
for ((i = 0; i < $((2 * LOAD_FACTOR)); i++)); do
while [ -e $dupe_run ]; do
- $DUPEREMOVE_PROG -dr --dedupe-options=same $testdir \
- >>$seqres.full 2>&1
+ # Run cmd in a subshell so that the golden output does not
+ # capture assertions that trigger when killall shoots down
+ # dupremove processes in an arbitrary order, which leaves the
+ # memory in an inconsistent state long enough for the assert
+ # to trip.
+ cmd="$DUPEREMOVE_PROG -dr --dedupe-options=same $testdir"
+ bash -c "$cmd" >> $seqres.full 2>&1
done 2>&1 | sed -e '/Terminated/d' &
dedup_pids="$! $dedup_pids"
done
next prev parent reply other threads:[~2021-07-20 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 1:08 [PATCHSET v2 0/1] fstests: random fixes Darrick J. Wong
2021-07-20 1:08 ` Darrick J. Wong [this message]
2021-07-22 6:37 ` [PATCH 1/1] generic/561: hide assertions when duperemove is killed Christoph Hellwig
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=162674330933.2650745.11380233368495712613.stgit@magnolia \
--to=djwong@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).