Lines Matching full:would

35 subject to the caveat that reads which would violate the hash will
54 accessed on a particular device.  It would be slow and wasteful to
304 to be authenticated against the file digest that would be returned by
363   would circumvent the data verification.
532   fs-verity from being used in cases where it would be helpful.
662 they are marked Uptodate.  Merely hooking ``->read_iter()`` would be
727 direct I/O would bypass fs-verity.
796     then you could simply do sha256(file) instead.  That would be much
801     first read.  However, it would be inefficient because every time a
828 :A: Write support would be very difficult and would require a
830     fs-verity.  Write support would require:
840     - Rebuilding the Merkle tree after every write, which would be
843       be used.  However, this would be far more complex.
881 :A: There are many reasons why this is not possible or would be very
888       the VFS to do the verification on its own.  Changing this would
891     - It would require defining a filesystem-independent way to store
900       So the verity metadata would have to be stored in an actual
901       file.  Using a separate file would be very ugly, since the
905       having it be in the same file would break applications unless
907       which would be complex and require changes to all filesystems.