linux-kernel - Re: [PATCH] staging: exfat: add exfat filesystem code to

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190917045640.GA2055638@kroah.com>
Date:   Tue, 17 Sep 2019 06:56:40 +0200
From:   'Greg KH' <gregkh@...uxfoundation.org>
To:     Namjae Jeon <namjae.jeon@...sung.com>
Cc:     devel@...verdev.osuosl.org, Namjae Jeon <linkinjeon@...il.com>,
        'Valdis Kletnieks' <valdis.kletnieks@...edu>,
        linux-kernel@...r.kernel.org, alexander.levin@...rosoft.com,
        sergey.senozhatsky@...il.com, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] staging: exfat: add exfat filesystem code to

On Tue, Sep 17, 2019 at 12:02:01PM +0900, Namjae Jeon wrote:
> We are excited to see this happening and would like to state that we appreciate
> time and
> effort which people put into upstreaming exfat. Thank you!
> 
> However, if possible, can we step back a little bit and re-consider it? We
> would prefer to see upstream the code which we are currently using in
> our products - sdfat - as this can be mutually benefitial from various
> points of view.

What is "different" in it from the code that is currently in linux-next?
What is supported "better"?  The code we have today seems to work for
people, so what are we missing here?

Also, submitting patches for this codebase to bring it up to the level
of functionality you need would be wonderful, can you do that?

thanks,

greg k-h