Lines Matching refs:handle

194 handle it in two different ways:
198    applications are usually prepared to handle this error (mv(1) for example
241 indexed by the file handle of the lower inode and a file handle of the
244 directory does not match the file handle stores in the index, that is an
499 handle of the lower layer root directory, along with the UUID of the lower
502 the lower root directory file handle and lower filesystem UUID are compared
516 the copied layers will fail the verification of the lower root file handle.
525 This is the list of cases that overlayfs doesn't currently handle:
593 On every copy_up, an NFS file handle of the lower inode, along with the
600 that the found lower directory file handle and lower filesystem UUID
601 match the origin file handle that was stored at copy_up time.  If a
615 hexadecimal representation of the copy up origin file handle.  For a
618 "trusted.overlay.upper" with an encoded file handle of the upper
621 When encoding a file handle from an overlay filesystem object, the
624 1. For a non-upper object, encode a lower file handle from lower inode
625 2. For an indexed object, encode a lower file handle from copy_up origin
627    encode an upper file handle from upper inode
629 The encoded overlay file handle includes:
637 When decoding an overlay file handle, the following steps are followed:
640 2. Decode the underlying filesystem file handle to underlying dentry.
641 3. For a lower file handle, lookup the handle in index directory by name.
643    overlay object that was deleted after its file handle was encoded.
649 Decoding a non-directory file handle may return a disconnected dentry.
655 "redirects" are not indexed, a lower file handle that was encoded from the
657 layer directory.  Similarly, a lower file handle that was encoded from a
660 directories that cannot be decoded from a lower file handle, these
661 directories are copied up on encode and encoded as an upper file handle.