[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878qvwlmhy.fsf@mailhost.krisman.be>
Date: Thu, 12 Sep 2024 15:07:05 -0400
From: Gabriel Krisman Bertazi <gabriel@...sman.be>
To: André Almeida <andrealmeid@...lia.com>
Cc: Hugh Dickins <hughd@...gle.com>, Andrew Morton
<akpm@...ux-foundation.org>, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, kernel-dev@...lia.com, Daniel Rosenberg
<drosen@...gle.com>, smcv@...labora.com, Christoph Hellwig <hch@....de>,
Theodore Ts'o <tytso@....edu>
Subject: Re: [PATCH v4 10/10] docs: tmpfs: Add casefold options
André Almeida <andrealmeid@...lia.com> writes:
> Document mounting options for casefold support in tmpfs.
>
> Signed-off-by: André Almeida <andrealmeid@...lia.com>
> ---
> Changes from v3:
> - Rewrote note about "this doesn't enable casefold by default" (Krisman)
> ---
> Documentation/filesystems/tmpfs.rst | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/Documentation/filesystems/tmpfs.rst b/Documentation/filesystems/tmpfs.rst
> index 56a26c843dbe..f72fcc0baef3 100644
> --- a/Documentation/filesystems/tmpfs.rst
> +++ b/Documentation/filesystems/tmpfs.rst
> @@ -241,6 +241,28 @@ 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-insensitive lookup support:
> +
> +================= ==============================================================
> +casefold Enable casefold support at this mount point using the given
> + argument as the encoding standard. Currently only UTF-8
> + encodings are supported. If no argument is used, it will load
> + the latest UTF-8 encoding available.
> +strict_encoding Enable strict encoding at this mount point (disabled by
> + default). In this mode, the filesystem refuses to create file
> + and directory with names containing invalid UTF-8 characters.
> +================= ==============================================================
> +
> +This option doesn't render the entire filesystem case-insensitive. One needs to
> +still set the casefold flag per directory, by flipping +F attribute in an empty
> +directory. Nevertheless, new directories will inherit the attribute. The
> +mountpoint itself will cannot be made case-insensitive.
s/will//
Other than that:
Reviewed-by: Gabriel Krisman Bertazi <krisman@...e.de>
> +
> +Example::
> +
> + $ mount -t tmpfs -o casefold=utf8-12.1.0,strict_encoding fs_name /mytmpfs
> + $ mount -t tmpfs -o casefold fs_name /mytmpfs
> +
>
> :Author:
> Christoph Rohland <cr@....com>, 1.12.01
> @@ -250,3 +272,5 @@ RAM/SWAP in 10240 inodes and it is only accessible by root.
> KOSAKI Motohiro, 16 Mar 2010
> :Updated:
> Chris Down, 13 July 2020
> +:Updated:
> + André Almeida, 23 Aug 2024
--
Gabriel Krisman Bertazi
Powered by blists - more mailing lists