From: Eric Biggers <ebiggers@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
David Sterba <dsterba@suse.com>, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Andrey Albershteyn <aalbersh@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, fsverity@lists.linux.dev
Subject: Re: [PATCH 07/16] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio
Date: Mon, 26 Jan 2026 12:53:01 -0800 [thread overview]
Message-ID: <20260126205301.GD30838@quark> (raw)
In-Reply-To: <20260126191102.GO5910@frogsfrogsfrogs>
On Mon, Jan 26, 2026 at 11:11:02AM -0800, Darrick J. Wong wrote:
> On Mon, Jan 26, 2026 at 05:50:53AM +0100, Christoph Hellwig wrote:
> > Issuing more reads on errors is not a good idea, especially when the
> > most common error here is -ENOMEM.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > fs/verity/pagecache.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/verity/pagecache.c b/fs/verity/pagecache.c
> > index 1efcdde20b73..63393f0f5834 100644
> > --- a/fs/verity/pagecache.c
> > +++ b/fs/verity/pagecache.c
> > @@ -22,7 +22,8 @@ struct page *generic_read_merkle_tree_page(struct inode *inode, pgoff_t index,
> > struct folio *folio;
> >
> > folio = __filemap_get_folio(inode->i_mapping, index, FGP_ACCESSED, 0);
> > - if (IS_ERR(folio) || !folio_test_uptodate(folio)) {
> > + if (PTR_ERR(folio) == -ENOENT ||
> > + !(IS_ERR(folio) && !folio_test_uptodate(folio))) {
>
> I don't understand this logic at all. If @folio is actually an
> ERR_PTR, then we dereference the non-folio to see if it's not uptodate?
>
> I think (given the previous revisions) that what you want is to initiate
> readahead if either there's no folio at all (ENOENT) or if there is a
> folio but it's not uptodate? But not if there's some other error
> (ENOMEM, EL3HLT, EFSCORRUPTED, etc)?
>
> So maybe you want:
>
> folio = __filemap_get_folio(...);
> if (!IS_ERR(folio)) {
> if (folio_test_uptodate(folio))
> return folio_file_page(folio);
> folio_put(folio);
> } else if (PTR_ERR(folio) == -ENOENT) {
> return ERR_CAST(folio);
> }
>
> if (num_ra_pages > 1)
> page_cache_ra_unbounded(&ractl, num_ra_pages, 0);
> folio = read_mapping_folio(inode->i_mapping, index, NULL);
> if (IS_ERR(folio))
> return ERR_CAST(folio);
>
> return folio_file_page(folio);
>
> <confused>
That version is wrong too: the condition 'PTR_ERR(folio) == -ENOENT' is
backwards.
This code gets replaced later in the series anyway. For this patch, we
could simply insert two lines:
folio = __filemap_get_folio(inode->i_mapping, index, FGP_ACCESSED, 0);
+ if (IS_ERR(folio) && folio != ERR_PTR(-ENOENT))
+ return folio;
Then for the final version in generic_readahead_merkle_tree(), one
option would be:
struct folio *folio;
folio = __filemap_get_folio(inode->i_mapping, index, FGP_ACCESSED, 0);
if (folio == ERR_PTR(-ENOENT) ||
(!IS_ERR(folio) && !folio_test_uptodate(folio))) {
DEFINE_READAHEAD(ractl, NULL, NULL, inode->i_mapping, index);
page_cache_ra_unbounded(&ractl, nr_pages, 0);
}
if (!IS_ERR(folio))
folio_put(folio);
Or as a diff from this series:
- if (PTR_ERR(folio) == -ENOENT ||
- !(IS_ERR(folio) && !folio_test_uptodate(folio))) {
+ if (folio == ERR_PTR(-ENOENT) ||
+ (!IS_ERR(folio) && !folio_test_uptodate(folio))) {
(Note that PTR_ERR() shouldn't be used before it's known that the
pointer is an error pointer.)
- Eric
next prev parent reply other threads:[~2026-01-26 20:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 4:50 fsverity cleanups, speedup and memory usage optimization v3 Christoph Hellwig
2026-01-26 4:50 ` [PATCH 01/16] fs,fsverity: reject size changes on fsverity files in setattr_prepare Christoph Hellwig
2026-01-26 4:50 ` [PATCH 02/16] fs,fsverity: clear out fsverity_info from common code Christoph Hellwig
2026-01-26 4:50 ` [PATCH 03/16] ext4: don't build the fsverity work handler for !CONFIG_FS_VERITY Christoph Hellwig
2026-01-26 12:22 ` Jan Kara
2026-01-26 19:27 ` Darrick J. Wong
2026-01-26 4:50 ` [PATCH 04/16] f2fs: " Christoph Hellwig
2026-01-26 4:50 ` [PATCH 05/16] fsverity: pass struct file to ->write_merkle_tree_block Christoph Hellwig
2026-01-26 4:50 ` [PATCH 06/16] fsverity: start consolidating pagecache code Christoph Hellwig
2026-01-26 4:50 ` [PATCH 07/16] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio Christoph Hellwig
2026-01-26 19:11 ` Darrick J. Wong
2026-01-26 20:53 ` Eric Biggers [this message]
2026-01-27 6:00 ` Christoph Hellwig
2026-01-27 6:20 ` Eric Biggers
2026-01-27 6:28 ` Darrick J. Wong
2026-01-27 6:38 ` Christoph Hellwig
2026-01-28 0:57 ` Eric Biggers
2026-01-27 6:36 ` Christoph Hellwig
2026-01-26 4:50 ` [PATCH 08/16] fsverity: kick off hash readahead at data I/O submission time Christoph Hellwig
2026-01-26 19:26 ` Darrick J. Wong
2026-01-26 20:37 ` Eric Biggers
2026-01-26 4:50 ` [PATCH 09/16] fsverity: constify the vi pointer in fsverity_verification_context Christoph Hellwig
2026-01-26 19:13 ` Darrick J. Wong
2026-01-28 3:22 ` Eric Biggers
2026-01-28 3:32 ` Christoph Hellwig
2026-01-28 3:41 ` Eric Biggers
2026-01-28 3:48 ` Christoph Hellwig
2026-01-26 4:50 ` [PATCH 10/16] fsverity: deconstify the inode pointer in struct fsverity_info Christoph Hellwig
2026-01-26 19:13 ` Darrick J. Wong
2026-01-26 4:50 ` [PATCH 11/16] fsverity: push out fsverity_info lookup Christoph Hellwig
2026-01-26 4:50 ` [PATCH 12/16] fs: consolidate fsverity_info lookup in buffer.c Christoph Hellwig
2026-01-26 12:25 ` Jan Kara
2026-01-26 19:17 ` Darrick J. Wong
2026-01-26 4:50 ` [PATCH 13/16] ext4: consolidate fsverity_info lookup Christoph Hellwig
2026-01-26 12:27 ` Jan Kara
2026-01-26 4:51 ` [PATCH 14/16] f2fs: " Christoph Hellwig
2026-01-26 4:51 ` [PATCH 15/16] btrfs: " Christoph Hellwig
2026-01-26 4:51 ` [PATCH 16/16] fsverity: use a hashtable to find the fsverity_info Christoph Hellwig
2026-01-26 19:35 ` Darrick J. Wong
2026-01-26 20:40 ` Eric Biggers
2026-01-27 6:15 ` Christoph Hellwig
2026-01-28 3:28 ` Eric Biggers
2026-01-28 3:35 ` Christoph Hellwig
2026-01-28 3:44 ` Eric Biggers
2026-01-28 3:48 ` Christoph Hellwig
2026-01-28 3:59 ` 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=20260126205301.GD30838@quark \
--to=ebiggers@kernel.org \
--cc=aalbersh@redhat.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--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=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--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