14 of read-only files.  Currently, it is supported by the ext4, f2fs, and
489 ext4  section in Filesystem support
492 ext4 supports fs-verity since Linux v5.4 and e2fsprogs v1.45.2.
494 To create verity files on an ext4 filesystem, the filesystem must have
499 currently ext4 only supports mounting a filesystem with the "verity"
502 ext4 sets the EXT4_VERITY_FL on-disk inode flag on verity files.  It
505 ext4 also supports encryption, which can be used simultaneously with
510 ext4 stores the verity metadata (Merkle tree and fsverity_descriptor)
514 be read/written internally by ext4 with only some relatively small
515 changes to ext4.  This approach avoids having to depend on the
516 EA_INODE feature and on rearchitecturing ext4's xattr support to
521 Currently, ext4 verity only supports the case where the Merkle tree
537 Like ext4, f2fs stores the verity metadata (Merkle tree and
539 64K boundary beyond i_size.  See explanation for ext4 above.
606 Block device based filesystems (e.g. ext4 and f2fs) in Linux also use
613 ext4 and f2fs also support encryption.  If a verity file is also
658     kvm-xfstests -c ext4,f2fs,btrfs -g verity
750       Data journalling is available on ext4, but is very slow.
807       filesystem block, and (b) ext4 and f2fs encryption doesn't