From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: new EOF fragmentation tests
Date: Mon, 24 Jun 2024 10:49:28 +0200 [thread overview]
Message-ID: <20240624084928.GA20314@lst.de> (raw)
In-Reply-To: <20240623130301.s2r2fv5qjaspmcxi@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Sun, Jun 23, 2024 at 09:03:01PM +0800, Zorro Lang wrote:
> > +# SPDX-License-Identifier: GPL-2.0
> > +# Copyright (c) 2019 Red Hat, Inc. All Rights Reserved.
> ^^^^
> Should I keep "2019" or change it to 2024, or no matter :)
No Red Hat employee has touched this since 2019. And my changes mostly
removed boilerplate code, so there isn't much of a point in adding
my copyright notice here.
> > +_scratch_mkfs 2>&1 >> $seqres.full
>
> Wrong order:) ">>$seqres.full 2>&1"
Ok.
> If a case has background process, better to do kill&wait in _cleanup,
> for unexpected Ctrl^C when fstests is running. e.g.
Ok.
>
> _cleanup{}
> {
> # try to kill all background processes
> wait
> cd /
> rm -r -f $tmp.*
> }
>
> I'm not sure if there's a good to way to do "kill all background
> processes" in this case, or if it's necessary. But a "wait" might
> be worth, to avoid the "Device Busy" error. Any thoughts?
No really sure, but I'll play around with a few variants.
next prev parent reply other threads:[~2024-06-24 8:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 5:38 xfs post-EOF block freeing fixes Christoph Hellwig
2024-06-23 5:38 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-06-23 13:03 ` Zorro Lang
2024-06-24 8:49 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 8:45 xfs post-EOF block freeing fixes v2 Christoph Hellwig
2024-09-24 8:45 ` [PATCH] xfs: new EOF fragmentation tests Christoph Hellwig
2024-09-24 15:03 ` Darrick J. Wong
2024-09-25 11:15 ` Zorro Lang
2024-09-26 12:31 ` Zorro Lang
2024-10-01 14:59 ` Darrick J. Wong
2024-10-02 13:38 ` Zorro Lang
2024-10-02 14:35 ` Brian Foster
2024-10-02 14:57 ` Darrick J. Wong
2024-10-02 15:56 ` Brian Foster
2024-10-02 20:04 ` Darrick J. Wong
2024-10-13 17:49 ` Zorro Lang
2024-10-14 6:07 ` Christoph Hellwig
2024-10-14 14:14 ` Zorro Lang
2024-10-14 15:24 ` Darrick J. Wong
2024-10-14 17:46 ` Zorro Lang
2024-10-15 3:39 ` Christoph Hellwig
2019-02-11 1:36 Dave Chinner
2019-02-11 1:55 ` Dave Chinner
2019-02-12 14:03 ` Brian Foster
2019-02-12 21:04 ` Dave Chinner
2019-02-13 13:39 ` Brian Foster
2019-02-16 10:04 ` Eryu Guan
2019-02-17 21:56 ` Dave Chinner
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=20240624084928.GA20314@lst.de \
--to=hch@lst.de \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.