From: Zorro Lang <zlang@kernel.org>
To: Avinesh Kumar <avinesh.kumar@suse.com>
Cc: fstests@vger.kernel.org, zlang@redhat.com, djwong@kernel.org
Subject: Re: [PATCH] xfs/654: don't complain if the healthmon xfs_io already exited
Date: Sat, 14 Nov 2026 22:56:02 +0800 [thread overview]
Message-ID: <avh2d1fvEpQzACN4@zlang-mailbox> (raw)
In-Reply-To: <20261111152024.163855-1-avinesh.kumar@suse.com>
On Wed, Nov 11, 2026 at 04:20:19PM +0100, Avinesh Kumar wrote:
> From: Avinesh Kumar <avinesh.kumar@suse.com>
>
> After the unmount, the test resumes the stopped xfs_io healthmon
> process, which reads the "filesystem unmounted" event, sees EOF, and
> exits on its own. The test then sends it a SIGTERM anyway in case it
> did not exit. If xfs_io has already exited and been reaped by the
> shell, kill prints "kill: (PID) - No such process" to stderr, which
> doesn't match the golden output:
>
> +/opt/xfstests/tests/xfs/654: line 50: kill: (170710) - No such process
> mount refcount is in range
> mount + healthmon refcount is in range
>
> Redirect kill's output to $seqres.full, as _kill_xfs_healer does.
>
> Fixes: 79f6b1c3 ("xfs: test health monitoring code")
> Signed-off-by: Avinesh Kumar <avinesh.kumar@suse.com>
> ---
Reviewed-by: Zorro Lang <zlang@kernel.org>
> tests/xfs/654 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/xfs/654 b/tests/xfs/654
> index 012f31a8..e8d815ae 100755
> --- a/tests/xfs/654
> +++ b/tests/xfs/654
> @@ -47,7 +47,7 @@ mon_nomount_refcount="$(_module_refcount xfs)"
> # Capture mod refcount after continuing healthmon (which should exit due to the
> # unmount) and killing it.
> kill -CONT $healer_pid
> -kill $healer_pid
> +kill $healer_pid &>> $seqres.full
> wait
> unset healer_pid
> nomon_nomount_refcount="$(_module_refcount xfs)"
> --
> 2.56.0
>
>
prev parent reply other threads:[~2026-11-14 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 15:20 [PATCH] xfs/654: don't complain if the healthmon xfs_io already exited Avinesh Kumar
2026-11-11 17:26 ` Christoph Hellwig
2026-11-14 14:56 ` Zorro Lang [this message]
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=avh2d1fvEpQzACN4@zlang-mailbox \
--to=zlang@kernel.org \
--cc=avinesh.kumar@suse.com \
--cc=djwong@kernel.org \
--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