Home
last modified time | relevance | path

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

/Linux-v6.6/fs/overlayfs/
Ddir.c183 if (attr->hardlink) { in ovl_create_real()
184 err = ovl_do_link(ofs, attr->hardlink, dir, newdentry); in ovl_create_real()
263 struct dentry *newdentry, bool hardlink) in ovl_instantiate() argument
274 if (!hardlink) { in ovl_instantiate()
305 if (hardlink) in ovl_instantiate()
330 if (!attr->hardlink && !IS_POSIXACL(udir)) in ovl_create_upper()
348 err = ovl_instantiate(dentry, inode, newdentry, !!attr->hardlink); in ovl_create_upper()
457 bool hardlink = !!cattr->hardlink; in ovl_create_over_whiteout() local
462 if (!hardlink) { in ovl_create_over_whiteout()
491 if (!hardlink && in ovl_create_over_whiteout()
[all …]
Doverlayfs.h785 struct dentry *hardlink; member
/Linux-v6.6/Documentation/admin-guide/sysctl/
Dfs.rst191 A long-standing class of security issues is the hardlink-based
194 is to cross privilege boundaries when following a given hardlink (i.e. a
195 root process follows a hardlink created by another user). Additionally,
200 When set to "0", hardlink creation behavior is unrestricted.
/Linux-v6.6/Documentation/filesystems/
Dxfs-online-fsck-design.rst4520 | to handle the maximum hardlink count of any file. |