Lines Matching refs:dentry

8 All filesystem operations require a dentry (or two) as a starting
13 different way to refer to a particular dentry.  As the alternative
20 string for any dentry, and how to find an appropriate dentry for any
48    to already have a (non-connected) dentry, and must be able to move
49    that dentry into place (based on the parent and name in the
51    it is a dcache invariant that directories only have one dentry.
55 a/ A dentry flag DCACHE_DISCONNECTED which is set on
56    any dentry that might not be part of the proper prefix.
58    dentry is noticed to be a child of a dentry which is in the proper
69     d_obtain_alias(inode) will return a dentry for the given inode.
70       If the inode already has a dentry, one of those is returned.
72         DCACHE_DISCONNECTED) dentry is allocated and attached.
73       In the case of a directory, care is taken that only one dentry
75     d_splice_alias(inode, dentry) will introduce a new dentry into the tree;
76       either the passed-in dentry or a preexisting alias for the given inode
78       It returns NULL when the passed-in dentry is used, following the calling
91       If inode is NULL, d_splice_alias(inode, dentry) is equivalent to
93 		d_add(dentry, inode), NULL
95       Similarly, d_splice_alias(ERR_PTR(err), dentry) = ERR_PTR(err)
99 		return d_splice_alias(inode, dentry);
110     Takes a dentry and creates a filehandle fragment which can later be used
111     to find or create a dentry for the same object.  The default
118     create a dentry for it (possibly with d_obtain_alias).
122     implied object and create a dentry for it (possibly with
126     When given a dentry for a directory, this should return  a dentry for
127     the parent.  Quite possibly the parent dentry will have been allocated
134     When given a parent dentry and a child dentry, this should find a name
135     in the directory identified by the parent dentry, which leads to the
136     object identified by the child dentry.  If no get_name function is