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
| ||
|
Date: Sun, 29 Apr 2018 22:07:26 +0200 From: Ondrej Zary <linux@...nbow-software.org> To: Greg KH <gregkh@...uxfoundation.org> Cc: Pavel Machek <pavel@....cz>, Matthew Wilcox <willy@...radead.org>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Moving unmaintained filesystems to staging On Sunday 29 April 2018 14:07:05 Greg KH wrote: > On Thu, Apr 26, 2018 at 08:11:08AM +0200, Pavel Machek wrote: > > On Wed 2018-04-25 08:46:02, Matthew Wilcox wrote: > > > Recently ncpfs got moved to staging. Also recently, we had some fuzzer > > > developers report bugs in hfs, which they deem a security hole because > > > Ubuntu attempts to automount an inserted USB device as hfs. > > > > We promise "no-regressions" for code in main repository, no such > > promise for staging. We have quite a lot of code without maintainer. > > > > Moving code to staging means it will get broken -- staging was not > > designed for this. I believe moving anything there is bad idea. > > > > Staging is for ugly code, not for code that needs new maintainter. > > Staging is used for getting code _out_ of the kernel tree as well as > _in_. We use it all the time to move code there, see if anyone shows up > in 6-8 months to say "I will fix this!", and if not, we delete it. > > Look at what just happened to IRDA in the 4.17-rc1 release as an example > of this. Really a "great" example of deleting working code :( -- Ondrej Zary
Powered by blists - more mailing lists