Lines Matching full:would

35 subject to the caveat that reads which would violate the hash will
60 accessed on a particular device.  It would be slow and wasteful to
274 to be authenticated against the file digest that would be returned by
331   would circumvent the data verification.
553 are marked Uptodate.  Merely hooking ``->read_iter()`` would be
620 direct I/O would bypass fs-verity.  (They also do the same for
690     then you could simply do sha256(file) instead.  That would be much
695     first read.  However, it would be inefficient because every time a
722 :A: Write support would be very difficult and would require a
724     fs-verity.  Write support would require:
734     - Rebuilding the Merkle tree after every write, which would be
737       be used.  However, this would be far more complex.
775 :A: There are many reasons why this is not possible or would be very
782       the VFS to do the verification on its own.  Changing this would
785     - It would require defining a filesystem-independent way to store
794       So the verity metadata would have to be stored in an actual
795       file.  Using a separate file would be very ugly, since the
799       having it be in the same file would break applications unless
801       which would be complex and require changes to all filesystems.