diff options
Diffstat (limited to 'Documentation/filesystems')
| -rw-r--r-- | Documentation/filesystems/nfs/Exporting | 27 | ||||
| -rw-r--r-- | Documentation/filesystems/nilfs2.txt | 4 | ||||
| -rw-r--r-- | Documentation/filesystems/overlayfs.txt | 34 | 
3 files changed, 55 insertions, 10 deletions
| diff --git a/Documentation/filesystems/nfs/Exporting b/Documentation/filesystems/nfs/Exporting index 520a4becb75c..63889149f532 100644 --- a/Documentation/filesystems/nfs/Exporting +++ b/Documentation/filesystems/nfs/Exporting @@ -56,13 +56,25 @@ a/ A dentry flag DCACHE_DISCONNECTED which is set on     any dentry that might not be part of the proper prefix.     This is set when anonymous dentries are created, and cleared when a     dentry is noticed to be a child of a dentry which is in the proper -   prefix.  - -b/ A per-superblock list "s_anon" of dentries which are the roots of -   subtrees that are not in the proper prefix.  These dentries, as -   well as the proper prefix, need to be released at unmount time.  As -   these dentries will not be hashed, they are linked together on the -   d_hash list_head. +   prefix.  If the refcount on a dentry with this flag set +   becomes zero, the dentry is immediately discarded, rather than being +   kept in the dcache.  If a dentry that is not already in the dcache +   is repeatedly accessed by filehandle (as NFSD might do), an new dentry +   will be a allocated for each access, and discarded at the end of +   the access. + +   Note that such a dentry can acquire children, name, ancestors, etc. +   without losing DCACHE_DISCONNECTED - that flag is only cleared when +   subtree is successfully reconnected to root.  Until then dentries +   in such subtree are retained only as long as there are references; +   refcount reaching zero means immediate eviction, same as for unhashed +   dentries.  That guarantees that we won't need to hunt them down upon +   umount. + +b/ A primitive for creation of secondary roots - d_obtain_root(inode). +   Those do _not_ bear DCACHE_DISCONNECTED.  They are placed on the +   per-superblock list (->s_roots), so they can be located at umount +   time for eviction purposes.  c/ Helper routines to allocate anonymous dentries, and to help attach     loose directory dentries at lookup time. They are: @@ -77,7 +89,6 @@ c/ Helper routines to allocate anonymous dentries, and to help attach        (such as an anonymous one created by d_obtain_alias), if appropriate.        It returns NULL when the passed-in dentry is used, following the calling        convention of ->lookup. -  Filesystem Issues  ----------------- diff --git a/Documentation/filesystems/nilfs2.txt b/Documentation/filesystems/nilfs2.txt index c0727dc36271..f2f3f8592a6f 100644 --- a/Documentation/filesystems/nilfs2.txt +++ b/Documentation/filesystems/nilfs2.txt @@ -25,8 +25,8 @@ available from the following download page.  At least "mkfs.nilfs2",  cleaner or garbage collector) are required.  Details on the tools are  described in the man pages included in the package. -Project web page:    http://nilfs.sourceforge.net/ -Download page:       http://nilfs.sourceforge.net/en/download.html +Project web page:    https://nilfs.sourceforge.io/ +Download page:       https://nilfs.sourceforge.io/en/download.html  List info:           http://vger.kernel.org/vger-lists.html#linux-nilfs  Caveats diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt index 8caa60734647..e6a5f4912b6d 100644 --- a/Documentation/filesystems/overlayfs.txt +++ b/Documentation/filesystems/overlayfs.txt @@ -156,6 +156,40 @@ handle it in two different ways:     root of the overlay.  Finally the directory is moved to the new     location. +There are several ways to tune the "redirect_dir" feature. + +Kernel config options: + +- OVERLAY_FS_REDIRECT_DIR: +    If this is enabled, then redirect_dir is turned on by  default. +- OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW: +    If this is enabled, then redirects are always followed by default. Enabling +    this results in a less secure configuration.  Enable this option only when +    worried about backward compatibility with kernels that have the redirect_dir +    feature and follow redirects even if turned off. + +Module options (can also be changed through /sys/module/overlay/parameters/*): + +- "redirect_dir=BOOL": +    See OVERLAY_FS_REDIRECT_DIR kernel config option above. +- "redirect_always_follow=BOOL": +    See OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW kernel config option above. +- "redirect_max=NUM": +    The maximum number of bytes in an absolute redirect (default is 256). + +Mount options: + +- "redirect_dir=on": +    Redirects are enabled. +- "redirect_dir=follow": +    Redirects are not created, but followed. +- "redirect_dir=off": +    Redirects are not created and only followed if "redirect_always_follow" +    feature is enabled in the kernel/module config. +- "redirect_dir=nofollow": +    Redirects are not created and not followed (equivalent to "redirect_dir=off" +    if "redirect_always_follow" feature is not enabled). +  Non-directories  --------------- |