Home
last modified time | relevance | path

Searched refs:fsverity_verify_page (Results 1 – 6 of 6) sorted by relevance

/kernel/linux/linux-5.10/include/linux/
Dfsverity.h143 bool fsverity_verify_page(struct page *page);
188 static inline bool fsverity_verify_page(struct page *page) in fsverity_verify_page() function
/kernel/linux/linux-5.10/fs/verity/
Dverify.c189 bool fsverity_verify_page(struct page *page) in fsverity_verify_page() function
205 EXPORT_SYMBOL_GPL(fsverity_verify_page);
/kernel/linux/linux-5.10/fs/ext4/
Dreadpage.c344 !fsverity_verify_page(page)) in ext4_mpage_readpages()
/kernel/linux/linux-5.10/Documentation/filesystems/
Dfsverity.rst484 Therefore, fs/verity/ provides a function fsverity_verify_page() which
488 fsverity_verify_page() will call back into the filesystem to read
491 fsverity_verify_page() returns false if verification failed; in this
497 fsverity_verify_page() currently only supports the case where the
500 In principle, fsverity_verify_page() verifies the entire path in the
503 fsverity_verify_page() only ascends the tree reading hash pages until
545 filesystems use fsverity_verify_page() to verify hole pages.
/kernel/linux/linux-5.10/fs/f2fs/
Dcompress.c1556 if (!verity || fsverity_verify_page(rpage)) { in f2fs_decompress_end_io()
Ddata.c216 if (fsverity_verify_page(page)) { in f2fs_verify_bio()
2131 !fsverity_verify_page(page)) { in f2fs_read_single_page()