Home
last modified time | relevance | path

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

/linux-6.1.9/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
275 if (!hardlink) { in ovl_instantiate()
306 if (hardlink) in ovl_instantiate()
331 if (!attr->hardlink && !IS_POSIXACL(udir)) in ovl_create_upper()
349 err = ovl_instantiate(dentry, inode, newdentry, !!attr->hardlink); in ovl_create_upper()
474 bool hardlink = !!cattr->hardlink; in ovl_create_over_whiteout() local
479 if (!hardlink) { in ovl_create_over_whiteout()
508 if (!hardlink && in ovl_create_over_whiteout()
[all …]
Doverlayfs.h659 struct dentry *hardlink; member
/linux-6.1.9/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.