Re: [PATCH v10 03/22] ovl: use core fsverity ensure info interface
Eric Biggers <[email protected]> Wed, 20 May 2026 19:07:19 +0000
| Newsgroups | dev.linux.lists.fsverity,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-unionfs,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <[email protected]> |
On Wed, May 20, 2026 at 02:37:01PM +0200, Andrey Albershteyn wrote: > fsverity now exposes fsverity_ensure_verity_info() which could be used > instead of opening file to ensure that fsverity info is loaded and > attached to inode. > > Signed-off-by: Andrey Albershteyn <[email protected]> > Acked-by: Amir Goldstein <[email protected]> > --- > fs/overlayfs/util.c | 14 +++----------- > 1 file changed, 3 insertions(+), 11 deletions(-) Reviewed-by: Eric Biggers <[email protected]> I'm still confused by the new implementation of fsverity_active() that got introduced by "fsverity: use a hashtable to find the fsverity_info", though. I should have caught this during review of that commit. For one its comment is outdated, but also the memory barrier seems to be specific to the fsverity_get_info() caller and probably should be moved to there. Anyway, that's not directly related to this patch. - Eric