Re: [PATCH] ovl: fix verity lazy-load guard broken by fsverity_active() semantic change

On Tue, May 05, 2026 at 02:00:16PM -0700, Eric Biggers wrote:
> On Tue, May 05, 2026 at 02:15:58PM -0400, Colin Walters wrote:
> > Commit f77f281b6118 ("fsverity: use a hashtable to find the fsverity_info")
> > that broke `ovl_ensure_verity_loaded` in the case when the inode was not in core.
> > 
> > The APIs here are in my opinion now confusing, but this patch intentionally
> > aims for a minimized fix by using `fsverity_get_info()` which ensures
> > the hash table is loaded.
> > 
> > Fixes: f77f281b6118 ("fsverity: use a hashtable to find the fsverity_info")
> > Cc: [email protected]
> > Link: https://github.com/bootc-dev/bootc/issues/2174
> > Signed-off-by: Colin Walters <[email protected]>
> 
> Reviewed-by: Eric Biggers <[email protected]>
> 
> I can take this through the fsverity tree as a fix for 7.1.  Amir, let
> me know if you'd prefer to take it instead.

I'll take this fix, but reading the commit message again, the
explanation makes no sense.  The issue has nothing to do with whether
the *inode* is in core or not.  And we aren't "loading a hash table".
The change in the order that we do the checks isn't mentioned, either.

I sent a v2 with an explanation that is much clearer, IMO.

I'll apply that version if there isn't any objection.

- Eric