Lines Matching full:underlying

32 In the special case of all overlay layers on the same underlying
34 filesystem and st_ino from the underlying filesystem.  This will
40 underlying filesystem, the same compliant behavior could be achieved
42 identifier from the real object st_ino and an underlying fsid index.
44 If all underlying filesystems support NFS file handles and export file
46 will use the high inode number bits for fsid.  Even when the underlying
49 case of underlying filesystems like xfs and tmpfs, which use 64bit inode
51 the underlying inode number does overflow into the high xino bits, overlay
187 underlying directory (upper or lower).
294  compared to direct access on underlying lower or upper filesystems
302     upper layer based on underlying filesystem permissions, again including
309 Check (b) ensures that no task gains permissions to underlying layers that
410 directory tree on the same or different underlying filesystem, and even
455 underlying filesystem for all layers making up the overlay.
457 If this feature is disabled or the underlying filesystem doesn't have
467 Changes to underlying filesystems
473 Changes to the underlying filesystems while part of a mounted overlay
474 filesystem are not allowed.  If the underlying filesystem is changed,
479 behavior on offline changes of the underlying lower layer is different
499 When the underlying filesystems supports NFS export and the "nfs_export"
520  - UUID of the underlying filesystem
521  - Underlying filesystem encoding of underlying inode
528 1. Find underlying layer by UUID and path type information.
529 2. Decode the underlying filesystem file handle to underlying dentry.
534    decoded underlying dentry, the path type and index inode, if found.
535 6. For a directory, use the connected underlying decoded dentry, path type