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.
63 must live on a read-write filesystem because they are independently
133   1024 and the minimum of the system page size and the filesystem
152 FS_IOC_ENABLE_VERITY causes the filesystem to build a Merkle tree for
153 the file and persist it to a filesystem-specific location associated
189 - ``ENOTTY``: this type of filesystem does not implement fs-verity
191   support; or the filesystem superblock has not had the 'verity'
192   feature enabled on it; or the filesystem does not support fs-verity
193   on this file.  (See `Filesystem support`_.)
196 - ``EROFS``: the filesystem is read-only
237 - ``ENOTTY``: this type of filesystem does not implement fs-verity
239   support, or the filesystem superblock has not had the 'verity'
240   feature enabled on it.  (See `Filesystem support`_.)
259 Another example is copying verity metadata when creating filesystem
308 this ioctl, the filesystem is allowed to just read the Merkle tree
320 - ``ENOTTY``: this type of filesystem does not implement fs-verity, or
323   support, or the filesystem superblock has not had the 'verity'
324   feature enabled on it.  (See `Filesystem support`_.)
406 The "blocks" here are not necessarily the same as "filesystem blocks".
565 Filesystem support
575 methods to read and write the verity metadata to a filesystem-specific
586 To create verity files on an ext4 filesystem, the filesystem must have
588 it.  "verity" is an RO_COMPAT filesystem feature, so once set, old
589 kernels will only be able to mount the filesystem readonly, and old
590 versions of e2fsck will be unable to check the filesystem.
592 Originally, an ext4 filesystem with the "verity" feature could only be
622 To create verity files on an f2fs filesystem, the filesystem must have
669 fsverity_verify_blocks() will call back into the filesystem to read
673 case, the filesystem must not set the folio Uptodate.  Following this,
680 However, for efficiency the filesystem may cache the hash blocks.
715 postprocessing step the filesystem enqueues the bio_post_read_ctx on a
756     different focuses.  fs-verity is a filesystem-level mechanism for
767     standalone filesystem feature, and it's testable like other
768     filesystem features e.g. with xfstests.
864     heavily frowned upon by most of the Linux filesystem developers.
870     local filesystems, but in principle any filesystem that can store
876     by ``fs/verity/`` also assume that the filesystem uses the Linux
879 :Q: Why is anything filesystem-specific at all?  Shouldn't fs-verity
886       filesystem is responsible for marking folios Uptodate via
891     - It would require defining a filesystem-independent way to store
895       filesystem block, and (b) ext4 and f2fs encryption doesn't
909     - It's desirable that FS_IOC_ENABLE_VERITY uses the filesystem's