Home
last modified time | relevance | path

Searched refs:whiteout (Results 1 – 4 of 4) sorted by relevance

/linux/fs/overlayfs/
H A Dsuper.c569 struct dentry *whiteout; in ovl_check_rename_whiteout() local
601 whiteout = ovl_lookup_upper_unlocked(ofs, name.name.name, in ovl_check_rename_whiteout()
603 err = PTR_ERR(whiteout); in ovl_check_rename_whiteout()
604 if (IS_ERR(whiteout)) in ovl_check_rename_whiteout()
607 err = ovl_upper_is_whiteout(ofs, whiteout); in ovl_check_rename_whiteout()
611 ovl_cleanup(ofs, workdir, whiteout); in ovl_check_rename_whiteout()
612 dput(whiteout); in ovl_check_rename_whiteout()
H A Dovl_entry.h89 struct dentry *whiteout; member
H A Dparams.c847 dput(ofs->whiteout); in ovl_free_fs()
/linux/Documentation/filesystems/
H A Doverlayfs.rst148 A whiteout is created as a character device with 0/0 device number or
149 as a zero-size regular file with the xattr "trusted.overlay.whiteout".
151 When a whiteout is found in the upper level of a merged directory, any
152 matching name in the lower level is ignored, and the whiteout itself
161 "trusted.overlay.whiteout", should be additionally marked by setting the xattr
163 This is needed to avoid the overhead of checking the "trusted.overlay.whiteout"
583 A lower dir with a regular whiteout will always be handled by the overlayfs
584 mount, so to support storing an effective whiteout file in an overlayfs mount an
585 alternative form of whiteout is supported. This form is a regular, zero-size
586 file with the "overlay.whiteout" xattr set, inside a directory with the
[all …]