Lines Matching refs:a

8 All filesystem operations require a dentry (or two) as a starting
9 point.  Local applications have a reference-counted hold on suitable
11 applications that access a filesystem via a remote filesystem protocol
12 such as NFS may not be able to hold such a reference, and so need a
13 different way to refer to a particular dentry.  As the alternative
22 This byte string will be called a "filehandle fragment" as it
33 The dcache normally contains a proper prefix of any given filesystem
37 maintained easily (by each object maintaining a reference count on
40 However when objects are included into the dcache by interpreting a
41 filehandle fragment, there is no automatic creation of a path prefix
47 2/ The dcache must be prepared for a newly found (via ->lookup) directory
48    to already have a (non-connected) dentry, and must be able to move
51    it is a dcache invariant that directories only have one dentry.
55 a/ A dentry flag DCACHE_DISCONNECTED which is set on
57    This is set when anonymous dentries are created, and cleared when a
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.
71       If it doesn't, a new anonymous (IS_ROOT and
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
85 For a filesystem to be exportable it must:
89       when ->lookup finds an inode for a given parent and name.
97       Typically the ->lookup routine will simply end with a:
106 super_block.  This field must point to a "struct export_operations"
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
112     implementation creates a filehandle fragment that encodes a 32bit inode
117     Given a filehandle fragment, this should find the implied object and
118     create a dentry for it (possibly with d_obtain_alias).
121     Given a filehandle fragment, this should find the parent of the
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
129     so any filehandle lookup that requires finding a parent will fail.
130     ->lookup("..") is *not* used as a default as it can leave ".." entries
134     When given a parent dentry and a child dentry, this should find a name
137     supplied, a default implementation is provided which uses vfs_readdir
143 together with a one byte "type".
147 nuls.  Rather, the encode_fh routine should choose a "type" which