From: Greg KH <gregkh@linuxfoundation.org>
To: "Gaoxiang (OS)" <gaoxiang25@huawei.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Al Viro <viro@ZenIV.linux.org.uk>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 00/13] NLS/UTF-8 Case-Insensitive lookups for ext4 and VFS proposal
Date: Mon, 5 Mar 2018 13:10:57 +0100 [thread overview]
Message-ID: <20180305121057.GA13048@kroah.com> (raw)
In-Reply-To: <9047C53C18267742AB12E43B65C7F9F70BCD386E@dggemi505-mbs.china.huawei.com>
On Fri, Jan 26, 2018 at 02:52:28AM +0000, Gaoxiang (OS) wrote:
>
> Sorry for bother, I mean you refer to sdcardfs,
> The current Samsung sdcardfs and esdfs are all fsstress broken for many issues,
> However we developed an another approach last year, in
>
> https://android-review.googlesource.com/#/c/kernel/common/+/574402/3/Documentation/filesystems/hwsdcardfs.txt
>
> We applied it on HUAWEI Mate 10 (pro), and the complete solution is
>
> https://android-review.googlesource.com/#/q/status:open+project:kernel/common+branch:android-4.4+topic:huawei_sdcardfs
>
> It supports stackable case-insensitive without modifing VFS smoothly,
> and we tested fsstress on the top and lower layers at the same time
> without any problem.
Any specific reason that filesystem code has not been submitted here for
inclusion upstream? It seems like all of the various sdcardfs
forks/rewrites need to be standardized upstream first to allow everyone
to benifit, instead of all of the duplicated efforts that are happening
right now :(
By getting yours, or someone's, code merged properly, that should reduce
the amount of duplication here.
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-05 12:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 2:53 [PATCH RFC v2 00/13] NLS/UTF-8 Case-Insensitive lookups for ext4 and VFS proposal Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 01/13] charsets: Introduce middle-layer for character encoding Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 02/13] charsets: ascii: Wrap ascii functions to charsets library Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 03/13] charsets: utf8: Add unicode character database files Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 04/13] scripts: add trie generator for UTF-8 Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 05/13] charsets: utf8: Introduce code for UTF-8 normalization Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 06/13] charsets: utf8: reduce the size of utf8data[] Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 07/13] charsets: utf8: Hook-up utf-8 code to charsets library Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 08/13] charsets: utf8: Introduce test module for kernel UTF-8 implementation Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 09/13] ext4: Add ignorecase mount option Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 10/13] ext4: Include encoding information on the superblock Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 11/13] fscrypt: Introduce charset-based matching functions Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 12/13] ext4: Support charset name matching Gabriel Krisman Bertazi
2018-01-25 2:53 ` [PATCH RFC v2 13/13] ext4: Implement ext4 dcache hooks for custom charsets Gabriel Krisman Bertazi
2018-01-25 3:16 ` [PATCH RFC v2 00/13] NLS/UTF-8 Case-Insensitive lookups for ext4 and VFS proposal Al Viro
2018-01-25 19:32 ` Theodore Ts'o
2018-01-26 2:52 ` Gaoxiang (OS)
2018-03-05 12:10 ` Greg KH [this message]
2018-02-06 2:24 ` Gabriel Krisman Bertazi
2018-02-06 3:21 ` Gao Xiang
2018-02-12 19:56 ` Gabriel Krisman Bertazi
2018-02-12 22:43 ` Gao Xiang
2018-02-13 22:20 ` Gabriel Krisman Bertazi
2018-02-14 12:27 ` Gao Xiang
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=20180305121057.GA13048@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gaoxiang25@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.