14 of read-only files.  Currently, it is supported by the ext4 and f2fs
393 fs-verity is currently supported by the ext4 and f2fs filesystems.
406 ext4  section in Filesystem support
409 ext4 supports fs-verity since Linux v5.4 and e2fsprogs v1.45.2.
411 To create verity files on an ext4 filesystem, the filesystem must have
416 currently ext4 only supports mounting a filesystem with the "verity"
419 ext4 sets the EXT4_VERITY_FL on-disk inode flag on verity files.  It
422 ext4 also supports encryption, which can be used simultaneously with
427 ext4 stores the verity metadata (Merkle tree and fsverity_descriptor)
431 be read/written internally by ext4 with only some relatively small
432 changes to ext4.  This approach avoids having to depend on the
433 EA_INODE feature and on rearchitecturing ext4's xattr support to
438 Currently, ext4 verity only supports the case where the Merkle tree
454 Like ext4, f2fs stores the verity metadata (Merkle tree and
456 64K boundary beyond i_size.  See explanation for ext4 above.
516 Block device based filesystems (e.g. ext4 and f2fs) in Linux also use
523 ext4 and f2fs also support encryption.  If a verity file is also
542 Files on ext4 and f2fs may contain holes.  Normally, ``->readpages()``
547 ext4 and f2fs disable direct I/O on verity files, since otherwise
568     kvm-xfstests -c ext4,f2fs -g verity
660       Data journalling is available on ext4, but is very slow.
691 :A: Only ext4 and f2fs support is implemented currently, but in
717       filesystem block, and (b) ext4 and f2fs encryption doesn't