From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 2/5] btrfs/199: skip on zoned devices
Date: Thu, 20 Aug 2026 22:37:20 -0700 [thread overview]
Message-ID: <aofkEIj3zkXhSRdb@infradead.org> (raw)
In-Reply-To: <20260819131606.1478488-3-johannes.thumshirn@wdc.com>
On Wed, Aug 19, 2026 at 03:16:02PM +0200, Johannes Thumshirn wrote:
> The test detects trimmed bytes via the used space of the loopback
> backing file, which requires the backing filesystem to support hole
> punching triggered by loop device discards. Zoned btrfs does not
> support fallocate/punch hole, so discards to the loop device are
> rejected ("operation not supported") and the test cannot measure
> anything meaningful.
>
> Skip the test when the scratch device is zoned.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-08-21 5:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 13:16 [PATCH v2 0/5] fstests: misc fixes for zoned btrfs Johannes Thumshirn
2026-08-19 13:16 ` [PATCH v2 1/5] common/btrfs: fix awk field separator in _check_temp_fsid Johannes Thumshirn
2026-08-21 5:36 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 2/5] btrfs/199: skip on zoned devices Johannes Thumshirn
2026-08-21 5:37 ` Christoph Hellwig [this message]
2026-08-19 13:16 ` [PATCH v2 3/5] generic/746: skip on zoned btrfs Johannes Thumshirn
2026-08-21 5:38 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 4/5] btrfs/284: skip on zoned devices Johannes Thumshirn
2026-08-21 5:39 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 5/5] generic/781: fix copyright Johannes Thumshirn
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=aofkEIj3zkXhSRdb@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.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.