From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 1/2] f2fs: use fsverity_verify_blocks() instead of fsverity_verify_page()
Date: Sat, 14 Feb 2026 12:33:10 -0800 [thread overview]
Message-ID: <20260214203311.9759-2-ebiggers@kernel.org> (raw)
In-Reply-To: <20260214203311.9759-1-ebiggers@kernel.org>
Replace the only remaining caller of fsverity_verify_page() with the
equivalent direct call to fsverity_verify_blocks(). No functional
change. This will allow fsverity_verify_page() to be removed.
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
fs/f2fs/compress.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
index 006a80acd1de..6d688835387d 100644
--- a/fs/f2fs/compress.c
+++ b/fs/f2fs/compress.c
@@ -1815,11 +1815,12 @@ static void f2fs_verify_cluster(struct work_struct *work)
struct page *rpage = dic->rpages[i];
if (!rpage)
continue;
- if (fsverity_verify_page(dic->vi, rpage))
+ if (fsverity_verify_blocks(dic->vi, page_folio(rpage),
+ PAGE_SIZE, 0))
SetPageUptodate(rpage);
else
ClearPageUptodate(rpage);
unlock_page(rpage);
}
--
2.53.0
next prev parent reply other threads:[~2026-02-14 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 20:33 [PATCH 0/2] fsverity: remove fsverity_verify_page() Eric Biggers
2026-02-14 20:33 ` Eric Biggers [this message]
2026-02-14 20:39 ` [PATCH 1/2] f2fs: use fsverity_verify_blocks() instead of fsverity_verify_page() Linus Torvalds
2026-02-14 20:48 ` Eric Biggers
2026-02-14 20:55 ` Linus Torvalds
2026-02-14 20:33 ` [PATCH 2/2] fsverity: remove fsverity_verify_page() 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=20260214203311.9759-2-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=chao@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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