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]

Date:   Mon, 30 Sep 2019 13:25:13 +0900
From:   "Namjae Jeon" <namjae.jeon@...sung.com>
To:     "'Dan Carpenter'" <dan.carpenter@...cle.com>,
        "'Greg KH'" <gregkh@...uxfoundation.org>
Cc:     <devel@...verdev.osuosl.org>, <linkinjeon@...il.com>,
        "'Valdis Kletnieks'" <valdis.kletnieks@...edu>,
        "'Sergey Senozhatsky'" <sergey.senozhatsky.work@...il.com>,
        <linux-kernel@...r.kernel.org>, <alexander.levin@...rosoft.com>,
        <sergey.senozhatsky@...il.com>, <linux-fsdevel@...r.kernel.org>,
        <sj1557.seo@...sung.com>, "'Ju Hyung Park'" <qkrwngud825@...il.com>
Subject: RE: [PATCH] staging: exfat: add exfat filesystem code to


> [..]
> > Put it in drivers/staging/sdfat/.
> >
> > But really we want someone from Samsung to say that they will treat
> > the staging version as upstream.  It doesn't work when people apply
> > fixes to their version and a year later back port the fixes into
> > staging.  The staging tree is going to have tons and tons of white space
> > fixes so backports are a pain.  All development needs to be upstream
> > first where the staging driver is upstream.  Otherwise we should just
> > wait for Samsung to get it read to be merged in fs/ and not through the
> > staging tree.
> Quite frankly,
> This whole thing came as a huge-huge surprise to us, we did not initiate
> upstreaming of exfat/sdfat code and, as of this moment, I'm not exactly
> sure that we are prepared for any immediate radical changes to our internal
> development process which people all of a sudden want from us. I need to
> discuss with related people on internal thread.
> please wait a while:)
We decide to contribute sdfat directly and treat upstream exfat.
Perhaps more time is needed for patch preparation(exfat rename + vfat removal
+ clean-up) and internal processes. After contributing sdfat v2.2.0 as the base,
We will also provide change-set of sdfat v2.3.0 later.

Thanks!
> 
> Thanks!
> >
> > regards,
> > dan carpenter
> >