Lines Matching refs:metacopy

368 When the "metacopy" feature is enabled, overlayfs will only copy
371 "trusted.overlayfs.metacopy" xattr which indicates that the upper file
374 the "trusted.overlayfs.metacopy" xattr is removed from the upper file.
382 parameter metacopy=on/off. Lastly, there is also a per mount option
383 metacopy=on/off to enable/disable this feature per mount.
385 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
393 conflict with metacopy=on, and will result in an error.
395 [*] redirect_dir=follow only conflicts with metacopy=on if upperdir=... is
402 With "metacopy" feature enabled, an overlayfs regular file may be a composition
429 when a "metacopy" file in one of the lower layers above it, has a "redirect"
448 digest of the lower file is added to the "trusted.overlay.metacopy"
450 each the time the metacopy file is opened.
453 metacopy file in the upper layer is guaranteed to match the content
468 for all metacopy files.  If additionally the untrusted lower
477     The metacopy digest is never generated or used. This is the
480     Whenever a metacopy files specifies an expected digest, the
482     generating a metacopy file the verity digest will be set in it
485     Same as "on", but additionally all metacopy files must specify a
507 different lower layer path, is allowed, unless the "index" or "metacopy"
521 For the "metacopy" feature, there is no verification mechanism at
540 "overlay.overlay.". So, a file with a "trusted.overlay.overlay.metacopy" xattr
542 "trusted.overlay.metacopy" xattr in the overlayfs mount. This can be nested by
623 "metacopy", "index", "xino" and "redirect_dir" features