From: "Darrick J. Wong" <djwong@kernel.org>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCH 2/8] generic/561: hide assertions when duperemove is killed
Date: Fri, 9 Jul 2021 18:25:08 -0700 [thread overview]
Message-ID: <20210710012508.GA11588@locust> (raw)
In-Reply-To: <e600bbe5-1914-5f93-aec8-bab97b16c732@oracle.com>
On Fri, Jul 09, 2021 at 04:38:46PM -0700, Allison Henderson wrote:
>
>
> On 7/6/21 5:21 PM, Darrick J. Wong wrote:
> > 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>
> > ---
> > tests/generic/561 | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> >
> > diff --git a/tests/generic/561 b/tests/generic/561
> > index bfd4443d..85037e50 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
> > + # Employ shell trickery here so that the golden output does not
> nit:
> I think I'd be more more specific with the commentary:
>
> # We run cmd in a bash shell so that the golden output ...
Ok, fixed.
--D
> > + # 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
> >
> Otherwise looks fine to me
> Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
next prev parent reply other threads:[~2021-07-10 1:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 0:21 [PATCHSET 0/8] fstests: random fixes Darrick J. Wong
2021-07-07 0:21 ` [PATCH 1/8] xfs/172: disable test when file writes don't use delayed allocation Darrick J. Wong
2021-07-09 23:38 ` Allison Henderson
2021-07-07 0:21 ` [PATCH 2/8] generic/561: hide assertions when duperemove is killed Darrick J. Wong
2021-07-09 23:38 ` Allison Henderson
2021-07-10 1:25 ` Darrick J. Wong [this message]
2021-07-07 0:21 ` [PATCH 3/8] shared/298: fix random deletion when filenames contain spaces Darrick J. Wong
2021-07-09 23:39 ` Allison Henderson
2021-07-07 0:21 ` [PATCH 4/8] dmthin: erase the metadata device properly before starting Darrick J. Wong
2021-07-09 23:39 ` Allison Henderson
2021-07-18 14:20 ` Eryu Guan
2021-07-18 14:32 ` Eryu Guan
2021-07-07 0:21 ` [PATCH 5/8] check: run _check_filesystems in an OOM-happy subshell Darrick J. Wong
2021-07-07 0:21 ` [PATCH 6/8] xfs/084: fix test program status collection and processing Darrick J. Wong
2021-07-07 0:21 ` [PATCH 7/8] generic/371: disable speculative preallocation regressions on XFS Darrick J. Wong
2021-07-09 23:50 ` Allison Henderson
2021-07-07 0:21 ` [PATCH 8/8] generic/019: don't dump cores when fio/fsstress hit io errors Darrick J. Wong
2021-07-09 23:39 ` Allison Henderson
2021-07-18 14:35 ` [PATCHSET 0/8] fstests: random fixes Eryu Guan
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=20210710012508.GA11588@locust \
--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).