diff options
| author | Colin Walters <walters@verbum.org> | 2026-05-05 15:42:57 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@kernel.org> | 2026-05-06 08:37:30 -0700 |
| commit | 0c8c88b8eb82a2a41bec5f17c076d6312dc40316 (patch) | |
| tree | 13966312e522ce15c4ea29ebdd063ff5fa513278 /tools/perf/scripts/python/bin/flamegraph-record | |
| parent | 7fd2df204f342fc17d1a0bfcd474b24232fb0f32 (diff) | |
ovl: fix verity lazy-load guard broken by fsverity_active() semantic change
Commit f77f281b6118 ("fsverity: use a hashtable to find the
fsverity_info") made fsverity_active() check whether the inode has the
verity flag, rather than whether the inode's fsverity_info is loaded.
This broke ovl_ensure_verity_loaded(), which wants to load the
fsverity_info for any verity inodes that haven't had it loaded yet.
Therefore, to check that the fsverity_info hasn't yet been loaded, use
fsverity_get_info(inode) == NULL instead of !fsverity_active(inode).
Also, since fsverity_get_info() now involves a hash table lookup, put
the more lightweight IS_VERITY() flag check first.
Fixes: f77f281b6118 ("fsverity: use a hashtable to find the fsverity_info")
Cc: stable@vger.kernel.org
Link: https://github.com/bootc-dev/bootc/issues/2174
Signed-off-by: Colin Walters <walters@verbum.org>
Acked-by: Amir Goldstein <amir73il@gmail.com>
Link: https://patch.msgid.link/20260505224257.23213-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/flamegraph-record')
0 files changed, 0 insertions, 0 deletions
