From: Eric Biggers <ebiggers@kernel.org>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com, fstests@vger.kernel.org
Subject: Re: [PATCH] btrfs: add a test for btrfs fsverity
Date: Thu, 4 Feb 2021 22:04:07 -0800 [thread overview]
Message-ID: <YBzf1z6EGCAK7JWN@sol.localdomain> (raw)
In-Reply-To: <c16cbe8ad5795f059af45bfe7cf673dab58028a2.1612468162.git.boris@bur.io>
Thanks for writing a test for this!
On Thu, Feb 04, 2021 at 03:24:26PM -0800, Boris Burkov wrote:
> There are some btrfs specific fsverity scenarios that don't map
> neatly onto the tests in generic/574, like holes, inline extents,
> and preallocated extents. Cover those in a btrfs specific test.
>
> That test relies on assumptions about how the Merkle tree is stored
> by ext4/f2fs which don't apply to btrfs, so we also test Merkle tree
> corruption here. This could be merged by some generic abstraction.
The only part of generic/574 that cares where the Merkle tree is stored is
_fsv_scratch_corrupt_merkle_tree(). Couldn't that be updated to handle btrfs?
> Finally, that test relies extensively on fiemap, which is currently
> broken on btrfs for offsets and sizes that don't align to PAGE_SIZE,
> so put a simple regular file case in this test for now, while we fix
> fiemap or generalize extent lookup.
fiemap is only used by _fsv_scratch_corrupt_bytes(). It just wants to know the
list of extents that intersect the requested byte range. Does that really not
work on btrfs if the range isn't page-aligned?
- Eric
next prev parent reply other threads:[~2021-02-05 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 23:24 [PATCH] btrfs: add a test for btrfs fsverity Boris Burkov
2021-02-05 6:04 ` Eric Biggers [this message]
2021-02-05 6:38 ` Boris Burkov
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=YBzf1z6EGCAK7JWN@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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