Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, stable@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/6] xfs: report healthy filesystem events in scrub stats
Date: Fri, 4 Sep 2026 08:48:30 +0200	[thread overview]
Message-ID: <appptaSxBjNe17JM@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <178850312540.1198660.5374727427398156944.stgit@frogsfrogsfrogs>

On Thu, Sep 03, 2026 at 11:26:17PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> LOLLM also notices that I forgot to expose the "clean bill of health"
> scrub stats.  Fix that.
> 
> Cc: <stable@vger.kernel.org> # v6.9
> Fixes: a1f3e0cca41036 ("xfs: update health status if we get a clean bill of health")
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> Assisted-by: LOLLM # finding obvious bugs
> ---
>  fs/xfs/scrub/stats.c |    1 +
>  1 file changed, 1 insertion(+)

Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>

> 
> 
> diff --git a/fs/xfs/scrub/stats.c b/fs/xfs/scrub/stats.c
> index f3f1fbfb6d9955..da0c05ffe5cd0b 100644
> --- a/fs/xfs/scrub/stats.c
> +++ b/fs/xfs/scrub/stats.c
> @@ -84,6 +84,7 @@ static const char *name_map[XFS_SCRUB_TYPE_NR] = {
>  	[XFS_SCRUB_TYPE_RGSUPER]	= "rgsuper",
>  	[XFS_SCRUB_TYPE_RTRMAPBT]	= "rtrmapbt",
>  	[XFS_SCRUB_TYPE_RTREFCBT]	= "rtrefcountbt",
> +	[XFS_SCRUB_TYPE_HEALTHY]	= "healthy",
>  };
>  
>  /* Format the scrub stats into a text buffer, similar to pcp style. */
> 
> 

  reply	other threads:[~2026-09-04  6:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  6:25 [PATCHSET] xfs: LLM-inspired bug fixes, part 11 Darrick J. Wong
2026-09-04  6:26 ` [PATCH 1/6] xfs: snapshot scrub stats when rendering them Darrick J. Wong
2026-09-04  6:48   ` Carlos Maiolino
2026-09-07  5:58   ` Christoph Hellwig
2026-09-08  4:43     ` Darrick J. Wong
2026-09-04  6:26 ` [PATCH 2/6] xfs: report healthy filesystem events in scrub stats Darrick J. Wong
2026-09-04  6:48   ` Carlos Maiolino [this message]
2026-09-07  5:58   ` Christoph Hellwig
2026-09-04  6:26 ` [PATCH 3/6] xfs: report runtime failures in scrub Darrick J. Wong
2026-09-04  6:59   ` Carlos Maiolino
2026-09-07  5:59   ` Christoph Hellwig
2026-09-04  6:26 ` [PATCH 4/6] xfs: remove redundant function declaration Darrick J. Wong
2026-09-04  6:59   ` Carlos Maiolino
2026-09-07  5:59   ` Christoph Hellwig
2026-09-04  6:27 ` [PATCH 5/6] xfs: snapshot old AGFL before rewriting it Darrick J. Wong
2026-09-04  7:34   ` Carlos Maiolino
2026-09-07  6:01   ` Christoph Hellwig
2026-09-04  6:27 ` [PATCH 6/6] xfs: bail out on bitmap errors in xrep_agfl_fill Darrick J. Wong
2026-09-04  7:38   ` Carlos Maiolino
2026-09-04 16:12     ` Darrick J. Wong
2026-09-04 16:13   ` [PATCH v1.1 " Darrick J. Wong
2026-09-04 19:11     ` Carlos Maiolino
2026-09-07  6:01     ` Christoph Hellwig
2026-09-07  6:28     ` Carlos Maiolino
2026-09-07  6:34       ` Carlos Maiolino
  -- strict thread matches above, loose matches on Subject: below --
2026-09-09  6:02 [PATCHSET 1/2] xfs: LLM-inspired bug fixes, part 11 Darrick J. Wong
2026-09-09  6:03 ` [PATCH 2/6] xfs: report healthy filesystem events in scrub stats Darrick J. Wong

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=appptaSxBjNe17JM@andromeda.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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