From: "Theodore Tso" <tytso@mit.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: Eric Biggers <ebiggers@kernel.org>,
fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
Andrey Albershteyn <aalbersh@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH] fsverity: add dependency on 64K or smaller pages
Date: Tue, 24 Feb 2026 10:32:28 -0500 [thread overview]
Message-ID: <20260224153228.GC16846@macsyma-wired.lan> (raw)
In-Reply-To: <20260224145156.GA13173@lst.de>
On Tue, Feb 24, 2026 at 03:51:56PM +0100, Christoph Hellwig wrote:
> Do we want to throw in the towel here for the forseable future and if we
> ever need to support fsverity on > 64k page size just do a on-disk
> version rev?
>
> Because if so we could just simply the pending xfs fsverity support to
> drop all the offset adjustment and simplify it a lot..
I wholeheartedly agree. Especially given the benefit of large folios,
increasing the base page size beyond 64k has enough downsides without
compelling upsides that can't be achieved via other means, I'm highly
skeptical that page sizes > 64k is going to be appealing for most
system designers. So trying to design in support for this possibility
in fsverrity is not worth it.
- Ted
next prev parent reply other threads:[~2026-02-24 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 20:45 [PATCH] fsverity: add dependency on 64K or smaller pages Eric Biggers
2026-02-24 13:55 ` David Sterba
2026-02-24 14:19 ` Arnd Bergmann
2026-02-24 14:51 ` Christoph Hellwig
2026-02-24 15:32 ` Theodore Tso [this message]
2026-02-24 15:24 ` Theodore Tso
2026-03-03 5:06 ` Eric Biggers
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=20260224153228.GC16846@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=aalbersh@kernel.org \
--cc=arnd@arndb.de \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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