From: Christoph Hellwig <hch@lst.de>
To: Omar Sandoval <osandov@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: BTRFS_IOC_ENCODED_READ testing
Date: Wed, 15 Feb 2023 08:31:25 +0100 [thread overview]
Message-ID: <20230215073125.GA31530@lst.de> (raw)
Hi Omar and other btrfs regulars,
what is the testing coverage of BTRFS_IOC_ENCODED_READ? I can't find
anyhing in xfstests that seems to specifically exercise it, although
I guess btrfs receive testing on a file system with compression and
a new enough btrfsprogs will eventually hit it. Are there any good
targeted tests somewhere else?
reply other threads:[~2023-02-15 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230215073125.GA31530@lst.de \
--to=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.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.