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
254   would circumvent the data verification.
481 are marked Uptodate.  Merely hooking ``->read_iter()`` would be
548 direct I/O would bypass fs-verity.  (They also do the same for
618     then you could simply do sha256(file) instead.  That would be much
623     first read.  However, it would be inefficient because every time a
650 :A: Write support would be very difficult and would require a
652     fs-verity.  Write support would require:
662     - Rebuilding the Merkle tree after every write, which would be
665       be used.  However, this would be far more complex.
703 :A: There are many reasons why this is not possible or would be very
710       the VFS to do the verification on its own.  Changing this would
713     - It would require defining a filesystem-independent way to store
722       So the verity metadata would have to be stored in an actual
723       file.  Using a separate file would be very ugly, since the
727       having it be in the same file would break applications unless
729       which would be complex and require changes to all filesystems.