filesystems/nfs/exporting.rst

7 --------
10 point.  Local applications have a reference-counted hold on suitable
16 server-reboot (among other things, though these tend to be the most
32 -------------
34 The dcache normally contains a proper prefix of any given filesystem
37 As normal access is by filename this prefix is created naturally and
42 filehandle fragment, there is no automatic creation of a path prefix
47    proper prefix. i.e that are not connected to the root.
48 2. The dcache must be prepared for a newly found (via ->lookup) directory
49    to already have a (non-connected) dentry, and must be able to move
51    ->lookup).   This is particularly needed for directories as
57    any dentry that might not be part of the proper prefix.
60    prefix.  If the refcount on a dentry with this flag set
68    without losing DCACHE_DISCONNECTED - that flag is only cleared when
75 b. A primitive for creation of secondary roots - d_obtain_root(inode).
77    per-superblock list (->s_roots), so they can be located at umount
93       either the passed-in dentry or a preexisting alias for the given inode
95       It returns NULL when the passed-in dentry is used, following the calling
96       convention of ->lookup.
99 -----------------
105       when ->lookup finds an inode for a given parent and name.
113       Typically the ->lookup routine will simply end with a::
143     ->lookup("..") is *not* used as a default as it can leave ".." entries
170 -----------------------
176   EXPORT_OP_NOWCC - disable NFSv3 WCC attributes on this filesystem
187     this on filesystems that have an expensive ->getattr inode operation,
191   EXPORT_OP_NOSUBTREECHK - disallow subtree checking on this fs
203   EXPORT_OP_CLOSE_BEFORE_UNLINK - always close cached files before unlinking
216   EXPORT_OP_REMOTE_FS - Backing storage for this filesystem is remote
226   EXPORT_OP_NOATOMIC_ATTR - Filesystem does not update attributes atomically
234   EXPORT_OP_FLUSH_ON_CLOSE - Filesystem flushes file data on close(2)
242   EXPORT_OP_ASYNC_LOCK - Indicates a capable filesystem to do async lock
244     it's own ->lock() functionality as core posix_lock_file() implementation
245     has no async lock request handling yet. For more information about how to
246     indicate an async lock request from a ->lock() file_operations struct, see