linux-ext4 - Re: [PATCH RFC v2 00/13] NLS/UTF-8 Case-Insensitive lookups for ext4 and VFS proposal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 5 Mar 2018 13:10:57 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Gaoxiang (OS)" <gaoxiang25@...wei.com>
Cc:     Theodore Ts'o <tytso@....edu>, Al Viro <viro@...IV.linux.org.uk>,
        "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH RFC v2 00/13] NLS/UTF-8 Case-Insensitive lookups for ext4
 and VFS proposal

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