Lines Matching full:layer
201 When renaming a directory that is on the lower layer or merged (i.e. the
202 directory was not created on the upper layer to start with) overlayfs can
258 Because lower layer redirects cannot be verified with the index, enabling
259 NFS export support on an overlay filesystem with no upper layer requires
310 upper layer based on underlying filesystem permissions, again including
349 top, lower2 the middle and lower3 the bottom layer.
351 Note: directory names containing colons can be provided as lower layer by
357 be configured as lower layer using the "lowerdir+" mount options and the
362 In the latter case, colons in lower layer directory names will be escaped
405 1) metadata from a file in the upper layer
407 2) st_ino and st_dev object identifier from a file in a lower layer
409 3) data from a file in another lower layer (further below)
411 The "lower data" file can be on any lower layer, except from the top most
412 lower layer.
414 Below the top most lower layer, any number of lower most layers may be defined
416 A normal lower layer is not allowed to be below a data-only layer, so single
430 to the absolute path of the "lower data" file in the "data-only" lower layer.
452 When a layer containing verity xattrs is used, it means that any such
453 metacopy file in the upper layer is guaranteed to match the content
466 layer is fully trusted (by using dm-verity or something similar), then
467 an untrusted lower layer can be used to supply validated file content
471 upper layer.
494 a very common practice. An overlay mount may use the same lower layer
495 path as another overlay mount and it may use a lower layer path that is
496 beneath or above the path of another overlay lower layer path.
498 Using an upper layer path and/or a workdir path that are already used by
502 upper layer and/or workdir path the behavior of the overlay is undefined,
505 Mounting an overlay using an upper layer path, where the upper layer path
507 different lower layer path, is allowed, unless the "index" or "metacopy"
511 handle of the lower layer root directory, along with the UUID of the lower
513 attribute on the upper layer root directory. On subsequent mount attempts,
564 done in the case when the file resides on a lower layer.
566 b) If a file residing on a lower layer is opened for read-only and then
570 c) If a file residing on a lower layer is being executed, then opening that
629 behavior on offline changes of the underlying lower layer is different
679 1. Find underlying layer by UUID and path type information.
693 When overlay filesystem has multiple lower layers, a middle layer
694 directory may have a "redirect" to lower directory. Because middle layer
697 layer directory. Similarly, a lower file handle that was encoded from a
702 On an overlay filesystem with no upper layer this mitigation cannot be