From: Eric Biggers <ebiggers@kernel.org>
To: Baokun Li <libaokun@huaweicloud.com>
Cc: fsverity@lists.linux.dev, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [QUESTION] Does fs-verity support large folios / large block size in ext4?
Date: Thu, 6 Nov 2025 12:44:51 -0800 [thread overview]
Message-ID: <20251106204451.GC7015@quark> (raw)
In-Reply-To: <10f8d4f8-14c8-46a9-be6e-07758b96bb59@huaweicloud.com>
On Thu, Nov 06, 2025 at 09:02:53PM +0800, Baokun Li wrote:
> I have recently been working on enabling large block size support in ext4.
> I had assumed that fs-verity does not support large folios / large block
> size. However, when testing with 64k LBS using:
>
> `kvm-xfstests -c ext4/64k -g verity -x encrypt`
>
> the tests passed successfully.
>
> Is this just a coincidence, or has fs-verity code already been updated to
> support large block size / large folios?
It might work already. I already added support for verifying data from
large folios several years ago:
commit 5d0f0e57ed900917836385527ce5b122fa1425a3
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Jan 27 14:15:29 2023 -0800
fsverity: support verifying data from large folios
Note that the Merkle tree block size is still limited to <= PAGE_SIZE.
But that's fine for now; generally people want 4K Merkle tree blocks
anyway. So the configuration in question, which should be getting
tested when you run that command and should theoretically work, should
be: filesystem_block_size=64K, PAGE_SIZE=4K, merkle_tree_block_size=4K.
Is there a git tree with your work that I can take a look at and confirm
that this is happening?
- Eric
next prev parent reply other threads:[~2025-11-06 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 13:02 [QUESTION] Does fs-verity support large folios / large block size in ext4? Baokun Li
2025-11-06 20:44 ` Eric Biggers [this message]
2025-11-07 3:25 ` Baokun Li
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=20251106204451.GC7015@quark \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=libaokun@huaweicloud.com \
--cc=tytso@mit.edu \
/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.