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>,
Matthew Wilcox <willy@infradead.org>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH v4 1/3] f2fs: remove unnecessary ClearPageUptodate in f2fs_verify_cluster()
Date: Tue, 17 Feb 2026 17:06:28 -0800 [thread overview]
Message-ID: <20260218010630.7407-2-ebiggers@kernel.org> (raw)
In-Reply-To: <20260218010630.7407-1-ebiggers@kernel.org>
Remove the unnecessary clearing of PG_uptodate. It's guaranteed to
already be clear.
Suggested-by: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
fs/f2fs/compress.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
index 006a80acd1de..355762d11e25 100644
--- a/fs/f2fs/compress.c
+++ b/fs/f2fs/compress.c
@@ -1817,12 +1817,10 @@ static void f2fs_verify_cluster(struct work_struct *work)
if (!rpage)
continue;
if (fsverity_verify_page(dic->vi, rpage))
SetPageUptodate(rpage);
- else
- ClearPageUptodate(rpage);
unlock_page(rpage);
}
f2fs_put_dic(dic, true);
}
--
2.53.0
next prev parent reply other threads:[~2026-02-18 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 1:06 [PATCH v4 0/3] fsverity: remove fsverity_verify_page() Eric Biggers
2026-02-18 1:06 ` Eric Biggers [this message]
2026-02-18 5:40 ` [PATCH v4 1/3] f2fs: remove unnecessary ClearPageUptodate in f2fs_verify_cluster() Christoph Hellwig
2026-02-18 1:06 ` [PATCH v4 2/3] f2fs: make f2fs_verify_cluster() partially large-folio-aware Eric Biggers
2026-02-18 5:40 ` Christoph Hellwig
2026-02-18 1:06 ` [PATCH v4 3/3] fsverity: remove fsverity_verify_page() Eric Biggers
2026-02-18 21:41 ` [PATCH v4 0/3] " 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=20260218010630.7407-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 \
--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