Hi--
On 3/23/21 12:59 PM, André Almeida wrote:
> Document mounting options to enable casefold support in tmpfs.
>
> Signed-off-by: André Almeida <andrealmeid@xxxxxxxxxxxxx>
> ---
> Documentation/filesystems/tmpfs.rst | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/Documentation/filesystems/tmpfs.rst b/Documentation/filesystems/tmpfs.rst
> index 0408c245785e..84c87c309bd7 100644
> --- a/Documentation/filesystems/tmpfs.rst
> +++ b/Documentation/filesystems/tmpfs.rst
> @@ -170,6 +170,32 @@ So 'mount -t tmpfs -o size=10G,nr_inodes=10k,mode=700 tmpfs /mytmpfs'
> will give you tmpfs instance on /mytmpfs which can allocate 10GB
> RAM/SWAP in 10240 inodes and it is only accessible by root.
>
> +tmpfs has the following mounting options for case-insesitive lookups support:
> +
> +========= ==============================================================
> +casefold Enable casefold support at this mount point using the given
> + argument as enconding. Currently only utf8 encondings are supported.
encoding. encodings
> +cf_strict Enable strict casefolding at this mouting point (disabled by
mount
> + default). This means that invalid strings should be reject by the
rejected
> + file system.
> +========= ==============================================================
> +
> +Note that this option doesn't enable casefold by default, one needs to set
default; one needs to set the
> +casefold flag per directory, setting the +F attribute in an empty directory. New
> +directories within a casefolded one will inherit the flag.
--
~Randy
