From: Christoph Hellwig <hch@infradead.org>
To: David Sterba <dsterba@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
David Sterba <dsterba@suse.com>,
fstests@vger.kernel.org, Josef Bacik <josef@toxicpanda.com>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 5/5] generic/733: disable for btrfs
Date: Thu, 21 Mar 2024 14:36:47 -0700 [thread overview]
Message-ID: <Zfyob_7NV9Kbd9pU@infradead.org> (raw)
In-Reply-To: <20240320155824.GD14596@suse.cz>
On Wed, Mar 20, 2024 at 04:58:24PM +0100, David Sterba wrote:
> It is a bug in the test, it should have been xfs specific and never
> promoted to generic/ and not affect btrfs unless explained how
> in the first place.
Well, the concept that reflinks are reasonably fast and are not live
locked by ongoing I/O seems pretty natural. But I guess we can't
just asusme quality of implementation everywhere, and do an opt-in
like _require_non_sucky_reflink. Either way we need to document
the assumptions and not add a magic exclude for a single fs.
next prev parent reply other threads:[~2024-03-21 21:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:11 [PATCH 0/5] Btrfs fstests fixups and updates David Sterba
2024-03-19 18:12 ` [PATCH 1/5] common/verity: use the correct options for btrfs-corrupt-block David Sterba
2024-03-20 9:58 ` Anand Jain
2024-03-20 15:23 ` David Sterba
2024-03-24 7:56 ` Anand Jain
2024-03-19 18:12 ` [PATCH 2/5] btrfs/131,btrfs/172,btrfs/206: add check for block-group-tree feature in btrfs David Sterba
2024-03-20 10:01 ` Anand Jain
2024-03-19 18:12 ` [PATCH 3/5] btrfs/330: add test to validate ro/rw subvol mounting David Sterba
2024-03-20 11:33 ` Anand Jain
2024-03-20 17:01 ` Filipe Manana
2024-03-21 3:51 ` Anand Jain
2024-03-19 18:12 ` [PATCH 4/5] common/rc: use proper temporary file path in _repair_test_fs() David Sterba
2024-03-20 11:35 ` Anand Jain
2024-03-19 18:12 ` [PATCH 5/5] generic/733: disable for btrfs David Sterba
2024-03-19 21:01 ` Christoph Hellwig
2024-03-19 21:10 ` Darrick J. Wong
2024-03-19 21:16 ` Christoph Hellwig
2024-03-20 15:58 ` David Sterba
2024-03-21 21:36 ` Christoph Hellwig [this message]
2024-03-21 21:52 ` Kent Overstreet
2024-03-22 15:08 ` Josef Bacik
2024-03-22 15:45 ` Darrick J. Wong
2024-03-22 18:28 ` Kent Overstreet
2024-03-20 9:49 ` [PATCH 0/5] Btrfs fstests fixups and updates Anand Jain
2024-03-20 15:26 ` David Sterba
2024-03-21 4:09 ` [PATCH] common/btrfs: set BTRFS_CORRUPT_BLOCK_OPT_<VALUE|OFFSET> Anand Jain
2024-03-21 11:13 ` Filipe Manana
2024-03-21 12:34 ` Anand Jain
2024-03-24 8:35 ` [PATCH 0/5] Btrfs fstests fixups and updates Anand Jain
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=Zfyob_7NV9Kbd9pU@infradead.org \
--to=hch@infradead.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.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