Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 01/13] add a "datacsum" group
Date: Mon, 5 Oct 2026 15:17:11 +0200	[thread overview]
Message-ID: <20261005131711.GH26805@lst.de> (raw)
In-Reply-To: <20260929013121.GD2705364@frogsfrogsfrogs>

On Mon, Sep 28, 2026 at 06:31:21PM -0700, Darrick J. Wong wrote:
> On Thu, Sep 24, 2026 at 12:07:42PM +0200, Christoph Hellwig wrote:
> > Add a group for test exercising data checksum functionality.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> >  doc/group-names.txt | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/doc/group-names.txt b/doc/group-names.txt
> > index ef6b8f51cf87..101c72688c02 100644
> > --- a/doc/group-names.txt
> > +++ b/doc/group-names.txt
> > @@ -34,6 +34,7 @@ dangerous		dangerous test that can crash the system
> >  dangerous_fuzzers	fuzzers that can crash your computer
> >  dangerous_selftest	selftests that crash/hang
> >  data			data loss checkers
> > +datacsum		data checksumming
> 
> Seems like a reasonable addition to me.  That said ... I bet at least
> btrfs/282 is a data checksum test that's incorrectly in the (metadata)
> scrub group.

I didn't really add any existing btrfs tests, but there's probably
a few.  Maybe the btrfs maintainers can help to populate the list?


           reply	other threads:[~2026-10-05 13:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260929013121.GD2705364@frogsfrogsfrogs>]

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=20261005131711.GH26805@lst.de \
    --to=hch@lst.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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