From: "André Almeida" <andrealmeid@collabora.com> To: Gabriel Krisman Bertazi <krisman@collabora.com> Cc: Hugh Dickins <hughd@google.com>, Andrew Morton <akpm@linux-foundation.org>, Alexander Viro <viro@zeniv.linux.org.uk>, smcv@collabora.com, kernel@collabora.com, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Rosenberg <drosen@google.com> Subject: Re: [RFC PATCH 4/4] docs: tmpfs: Add casefold options Date: Wed, 24 Mar 2021 17:47:12 -0300 [thread overview] Message-ID: <4058c0b9-d940-f069-8b31-39cd7ae16062@collabora.com> (raw) In-Reply-To: <87o8f9bjiw.fsf@collabora.com> Hi Gabriel, Às 19:19 de 23/03/21, Gabriel Krisman Bertazi escreveu: > André Almeida <andrealmeid@collabora.com> writes: > >> Document mounting options to enable casefold support in tmpfs. >> >> Signed-off-by: André Almeida <andrealmeid@collabora.com> >> --- >> 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. >> +cf_strict Enable strict casefolding at this mouting point (disabled by >> + default). This means that invalid strings should be reject by the >> + file system. > > strict mode refers to the encoding, not exactly casefold. Maybe we > could have a parameter encoding_flags that accepts the flag 'strict'. > This would make it closer to the ext4 interface. What are the other enconding flags? Or is this more about having a properly extensible interface? > Alternatively, call this option strict_encoding. > Thanks, André
prev parent reply other threads:[~2021-03-24 20:47 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 19:59 [RFC PATCH 0/4] mm: shmem: Add case-insensitive support for tmpfs André Almeida 2021-03-23 19:59 ` [RFC PATCH 1/4] Revert "libfs: unexport generic_ci_d_compare() and generic_ci_d_hash()" André Almeida 2021-03-23 20:15 ` Matthew Wilcox 2021-03-24 20:09 ` André Almeida 2021-03-23 19:59 ` [RFC PATCH 2/4] mm: shmem: Support case-insensitive file name lookups André Almeida 2021-03-23 20:18 ` Gabriel Krisman Bertazi 2021-03-24 20:17 ` André Almeida 2021-03-23 23:19 ` Al Viro 2021-03-24 20:44 ` André Almeida 2021-03-23 19:59 ` [RFC PATCH 3/4] mm: shmem: Add IOCTL support for tmpfs André Almeida 2021-03-23 22:15 ` Gabriel Krisman Bertazi 2021-03-23 19:59 ` [RFC PATCH 4/4] docs: tmpfs: Add casefold options André Almeida 2021-03-23 21:58 ` Randy Dunlap 2021-03-25 14:27 ` André Almeida 2021-03-23 22:19 ` Gabriel Krisman Bertazi 2021-03-24 20:47 ` André Almeida [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4058c0b9-d940-f069-8b31-39cd7ae16062@collabora.com \ --to=andrealmeid@collabora.com \ --cc=akpm@linux-foundation.org \ --cc=drosen@google.com \ --cc=hughd@google.com \ --cc=kernel@collabora.com \ --cc=krisman@collabora.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=smcv@collabora.com \ --cc=viro@zeniv.linux.org.uk \ --subject='Re: [RFC PATCH 4/4] docs: tmpfs: Add casefold options' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).