Home
last modified time | relevance | path

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

/Linux-v4.19/fs/overlayfs/
Ddir.c162 if (attr->hardlink) { in ovl_create_real()
163 err = ovl_do_link(attr->hardlink, dir, newdentry); in ovl_create_real()
240 struct dentry *newdentry, bool hardlink) in ovl_instantiate() argument
249 if (!hardlink) { in ovl_instantiate()
278 if (hardlink) in ovl_instantiate()
302 if (!attr->hardlink && !IS_POSIXACL(udir)) in ovl_create_upper()
320 err = ovl_instantiate(dentry, inode, newdentry, !!attr->hardlink); in ovl_create_upper()
444 bool hardlink = !!cattr->hardlink; in ovl_create_over_whiteout() local
449 if (!hardlink) { in ovl_create_over_whiteout()
474 if (!hardlink && in ovl_create_over_whiteout()
[all …]
Doverlayfs.h395 struct dentry *hardlink; member
/Linux-v4.19/Documentation/sysctl/
Dfs.txt207 A long-standing class of security issues is the hardlink-based
210 is to cross privilege boundaries when following a given hardlink (i.e. a
211 root process follows a hardlink created by another user). Additionally,
216 When set to "0", hardlink creation behavior is unrestricted.
/Linux-v4.19/Documentation/filesystems/pohmelfs/
Dnetwork_protocol.txt117 @start - 1 for symlink, 0 for hardlink.