From: "hch@lst.de" <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: "hch@lst.de" <hch@lst.de>, Hans Holmberg <Hans.Holmberg@wdc.com>,
Zorro Lang <zlang@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Matias Bj??rling <Matias.Bjorling@wdc.com>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"daeho43@gmail.com" <daeho43@gmail.com>
Subject: Re: [PATCH] generic: add gc stress test
Date: Thu, 9 May 2024 14:54:12 +0200 [thread overview]
Message-ID: <20240509125412.GA12191@lst.de> (raw)
In-Reply-To: <20240509094208.ulez6lg7ymesmhej@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Thu, May 09, 2024 at 05:42:08PM +0800, Zorro Lang wrote:
> Hmm, what kind of situation is this _expected_failure for?
Well, the one we are talking about here. We have a new and useful
test, and a file systems fails it because it has a bug.
Personally I'd be fine with just letting it fail, but you seemed to
indicate that this is a reason to not merge the test yet.
> I hope we can fix the obvious case issue in reviewing phase, or deal with the
> failure by 1) or 2). For this patch, I think we can find a way to avoid the
> failure for btrfs, or let this test "not supported" by btrfs. Or any other
> better ideas :)
It is a normal use case that every file system should handle and btrfs
developers are looking into it, but it might take a while.
next prev parent reply other threads:[~2024-05-09 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 11:23 [PATCH] generic: add gc stress test Hans Holmberg
2024-04-16 9:07 ` Hans Holmberg
2024-04-16 18:54 ` Darrick J. Wong
2024-04-17 12:43 ` Zorro Lang
2024-04-17 13:21 ` Hans Holmberg
2024-04-17 14:06 ` Zorro Lang
2024-04-17 14:45 ` Hans Holmberg
2024-05-08 7:08 ` Hans Holmberg
2024-05-08 8:51 ` Zorro Lang
2024-05-08 9:28 ` Qu Wenruo
2024-05-08 11:02 ` Johannes Thumshirn
2024-05-09 5:43 ` hch
2024-05-09 9:42 ` Zorro Lang
2024-05-09 12:54 ` hch [this message]
2024-05-10 3:21 ` Zorro Lang
2024-05-11 13:08 ` Hans Holmberg
2024-05-12 16:54 ` Johannes Thumshirn
2024-05-12 16:56 ` Johannes Thumshirn
2024-05-13 7:33 ` Qu Wenruo
2024-05-14 8:02 ` Hans Holmberg
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=20240509125412.GA12191@lst.de \
--to=hch@lst.de \
--cc=Damien.LeMoal@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=bvanassche@acm.org \
--cc=daeho43@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-btrfs@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.