From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Cc: linux-fsdevel@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] fsverity: support verifying data from large folios
Date: Fri, 3 Feb 2023 13:58:35 -0800 [thread overview]
Message-ID: <Y92DiwxOmc+EE+Tu@sol.localdomain> (raw)
In-Reply-To: <20230127221529.299560-1-ebiggers@kernel.org>
On Fri, Jan 27, 2023 at 02:15:29PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Try to make fs/verity/verify.c aware of large folios. This includes
> making fsverity_verify_bio() support the case where the bio contains
> large folios, and adding a function fsverity_verify_folio() which is the
> equivalent of fsverity_verify_page().
>
> There's no way to actually test this with large folios yet, but I've
> tested that this doesn't cause any regressions.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>
> This patch is targeting 6.3, and it applies to
> https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-next
> Note: to avoid a cross-tree dependency, in fs/buffer.c I used
> page_folio(bh->b_page) instead of bh->b_folio.
>
> Documentation/filesystems/fsverity.rst | 20 ++++++------
> fs/buffer.c | 3 +-
> fs/verity/verify.c | 43 +++++++++++++-------------
> include/linux/fsverity.h | 15 ++++++---
> 4 files changed, 44 insertions(+), 37 deletions(-)
Applied to https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-next
- Eric
prev parent reply other threads:[~2023-02-03 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 22:15 [PATCH] fsverity: support verifying data from large folios Eric Biggers
2023-02-03 21:58 ` Eric Biggers [this message]
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=Y92DiwxOmc+EE+Tu@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).