public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>,
	Filipe Manana <fdmanana@kernel.org>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: a new test case to verify scrub and rescue=idatacsums
Date: Tue, 13 May 2025 20:27:22 +0930	[thread overview]
Message-ID: <e01c7c8e-e7e9-472b-b0d2-89c2cf12b7a5@gmx.com> (raw)
In-Reply-To: <f442c391-cb4d-4b9b-ae1d-e38d2d573c25@oracle.com>



在 2025/5/13 19:27, Anand Jain 写道:
[...]
>>>
>>> Makes sense.
>>>
>>> As there is no way to check if the kernel has commit fix 6aecd91a5c5b
>>> testcase will crash the system. That's a bit concerning.
>>
>> In that case you can add the test case to dangerous group at merge time.
>>
> 
> Oh, right — we can use dangerous.
> 
> I thought you were still sending v2 with Filipe's review comments?
> 

Well, you reviewed the v2 version and applied, thus I guess it's easier 
to add the group on your side:

https://lore.kernel.org/linux-btrfs/60d18eaa-c6b0-45f3-952a-437abfd25636@oracle.com/

Thanks,
Qu


      reply	other threads:[~2025-05-13 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  5:25 [PATCH] fstests: btrfs: a new test case to verify scrub and rescue=idatacsums Qu Wenruo
2025-05-12  5:59 ` Johannes Thumshirn
2025-05-12  7:44 ` Filipe Manana
2025-05-12  7:50   ` Qu Wenruo
2025-05-12  7:54     ` Filipe Manana
2025-05-13  8:54       ` Anand Jain
2025-05-13  8:57         ` Qu Wenruo
2025-05-13  9:57           ` Anand Jain
2025-05-13 10:57             ` Qu Wenruo [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=e01c7c8e-e7e9-472b-b0d2-89c2cf12b7a5@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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