public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 3/8] xfs/*: clean up _cleanup override
Date: Fri, 27 May 2022 09:39:49 +1000	[thread overview]
Message-ID: <20220526233949.GB3923443@dread.disaster.area> (raw)
In-Reply-To: <20220526150417.bw3zpwiqcm5fkysn@zlang-mailbox>

On Thu, May 26, 2022 at 11:04:17PM +0800, Zorro Lang wrote:
> On Wed, May 25, 2022 at 01:13:36AM +0800, Zorro Lang wrote:
> > On Tue, May 24, 2022 at 01:42:15PM +0300, Amir Goldstein wrote:
> > > On Tue, May 24, 2022 at 12:41 PM Dave Chinner <david@fromorbit.com> wrote:
> > > >
> > > > From: Dave Chinner <dchinner@redhat.com>
> > > >
> > > > Use a local cleanup function and _register_cleanup properly.
> > > >
> > > > Remove local cleanups that just do what the standard _cleanup and
> > > > test exist does.
> > > >
> > > > Remove local cleanups that just remove test files and then do
> > > > standard _cleanup functionality.
> > > 
> > > As I mentioned in response to the cover letter, the call to _cleanup()
> > > can and I think should be chained implicitly, but I am still waiting
> > > for your response regarding the tests where generic _cleanup is not
> > > desired.
> > > 
> > > >
> > > > Signed-off-by: Dave Chinner <dchinner@redhat.com>
> > > > ---
> > > >  tests/xfs/004     |  7 -------
> > > >  tests/xfs/006     |  7 ++++---
> > 
> > [snap]
> > 
> > > > diff --git a/tests/xfs/006 b/tests/xfs/006
> > > > index cecceaa3..fd8d8071 100755
> > > > --- a/tests/xfs/006
> > > > +++ b/tests/xfs/006
> > > > @@ -11,11 +11,10 @@
> > > >  _begin_fstest auto quick mount eio
> > > >
> > > >  # Override the default cleanup function.
> > > > -_cleanup()
> > > > +_dmerror_cleanup()
> > > >  {
> > > > -       cd /
> > > > -       rm -f $tmp.*
> > > >         _dmerror_cleanup
> > > 
> > > That looks recursive.
> > 
> > Yes, but this _dmerror_cleanup() won't be run. This function will be covered by
> > the _dmerror_cleanup() in common/dmerror, when this case ". ./common/dmerror"
> > several lines later. So the later _cleanup won't be run. So this place and other
> > places similar with this need to change.
> 
> Hi Dave,
> 
> Are you going to fix this issue or making more changes on this patchset?
> If not, I'll merge this patchset tomorrow (Friday) by changing above
> _dmerror_cleanup to _dm_error_cleanup. Then give merged patches a regression
> on Saturday. What do you think?

I posted this patchset as an RFC, not as a candidate for merging.
It's not ready for merging yet.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2022-05-26 23:39 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 ` [PATCH 2/8] fstests: _cleanup overrides are messy Dave Chinner
2022-05-24 16:16   ` 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 [this message]
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=20220526233949.GB3923443@dread.disaster.area \
    --to=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