Lines Matching full:filesystem

15 btrfs filesystems.  Like fscrypt, not too much filesystem-specific
22 causes the filesystem to build a Merkle tree for the file and persist
23 it to a filesystem-specific location associated with the file.
69 must live on a read-write filesystem because they are independently
124   necessarily the same as the filesystem block size.
139 FS_IOC_ENABLE_VERITY causes the filesystem to build a Merkle tree for
140 the file and persist it to a filesystem-specific location associated
176 - ``ENOTTY``: this type of filesystem does not implement fs-verity
178   support; or the filesystem superblock has not had the 'verity'
179   feature enabled on it; or the filesystem does not support fs-verity
180   on this file.  (See `Filesystem support`_.)
183 - ``EROFS``: the filesystem is read-only
224 - ``ENOTTY``: this type of filesystem does not implement fs-verity
226   support, or the filesystem superblock has not had the 'verity'
227   feature enabled on it.  (See `Filesystem support`_.)
289 this ioctl, the filesystem is allowed to just read the Merkle tree
301 - ``ENOTTY``: this type of filesystem does not implement fs-verity, or
304   support, or the filesystem superblock has not had the 'verity'
305   feature enabled on it.  (See `Filesystem support`_.)
385 The "blocks" here are not necessarily the same as "filesystem blocks".
473 Filesystem support
483 methods to read and write the verity metadata to a filesystem-specific
494 To create verity files on an ext4 filesystem, the filesystem must have
496 it.  "verity" is an RO_COMPAT filesystem feature, so once set, old
497 kernels will only be able to mount the filesystem readonly, and old
498 versions of e2fsck will be unable to check the filesystem.  Moreover,
499 currently ext4 only supports mounting a filesystem with the "verity"
522 block size, filesystem block size, and page size are all the same.  It
530 To create verity files on an f2fs filesystem, the filesystem must have
578 fsverity_verify_page() will call back into the filesystem to read
582 case, the filesystem must not set the page Uptodate.  Following this,
592 efficiency the filesystem may cache the hash pages.  Therefore,
627 postprocessing step the filesystem enqueues the bio_post_read_ctx on a
668     different focuses.  fs-verity is a filesystem-level mechanism for
679     standalone filesystem feature, and it's testable like other
680     filesystem features e.g. with xfstests.
776     heavily frowned upon by most of the Linux filesystem developers.
782     local filesystems, but in principle any filesystem that can store
788     by ``fs/verity/`` also assume that the filesystem uses the Linux
791 :Q: Why is anything filesystem-specific at all?  Shouldn't fs-verity
798       filesystem is responsible for marking pages Uptodate via
803     - It would require defining a filesystem-independent way to store
807       filesystem block, and (b) ext4 and f2fs encryption doesn't
821     - It's desirable that FS_IOC_ENABLE_VERITY uses the filesystem's