Home
last modified time | relevance | path

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

/Linux-v5.4/fs/overlayfs/
Ddir.c159 if (attr->hardlink) { in ovl_create_real()
160 err = ovl_do_link(attr->hardlink, dir, newdentry); in ovl_create_real()
237 struct dentry *newdentry, bool hardlink) in ovl_instantiate() argument
246 if (!hardlink) { in ovl_instantiate()
275 if (hardlink) in ovl_instantiate()
299 if (!attr->hardlink && !IS_POSIXACL(udir)) in ovl_create_upper()
317 err = ovl_instantiate(dentry, inode, newdentry, !!attr->hardlink); in ovl_create_upper()
440 bool hardlink = !!cattr->hardlink; in ovl_create_over_whiteout() local
445 if (!hardlink) { in ovl_create_over_whiteout()
474 if (!hardlink && in ovl_create_over_whiteout()
[all …]
Doverlayfs.h407 struct dentry *hardlink; member
/Linux-v5.4/Documentation/admin-guide/sysctl/
Dfs.rst222 A long-standing class of security issues is the hardlink-based
225 is to cross privilege boundaries when following a given hardlink (i.e. a
226 root process follows a hardlink created by another user). Additionally,
231 When set to "0", hardlink creation behavior is unrestricted.