Home
last modified time | relevance | path

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

/linux/fs/overlayfs/
H A Ddir.c174 if (attr->hardlink) { in ovl_create_real()
175 err = ovl_do_link(ofs, attr->hardlink, dir, newdentry); in ovl_create_real()
286 struct dentry *newdentry, bool hardlink, struct file *tmpfile) in ovl_instantiate() argument
296 if (!hardlink) { in ovl_instantiate()
331 if (hardlink) in ovl_instantiate()
373 err = ovl_instantiate(dentry, inode, newdentry, !!attr->hardlink, NULL); in ovl_create_upper()
480 bool hardlink = !!cattr->hardlink; in ovl_create_over_whiteout() local
485 if (!hardlink) { in ovl_create_over_whiteout()
518 if (!hardlink && in ovl_create_over_whiteout()
531 if (!hardlink) { in ovl_create_over_whiteout()
[all …]
H A Doverlayfs.h905 struct dentry *hardlink; member
/linux/Documentation/admin-guide/sysctl/
H A Dfs.rst196 A long-standing class of security issues is the hardlink-based
199 is to cross privilege boundaries when following a given hardlink (i.e. a
200 root process follows a hardlink created by another user). Additionally,
205 When set to "0", hardlink creation behavior is unrestricted.
/linux/Documentation/filesystems/xfs/
H A Dxfs-online-fsck-design.rst4347 | to handle the maximum hardlink count of any file. |