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
| ||
|
Message-ID: <20180426025717.GA32430@bombadil.infradead.org> Date: Wed, 25 Apr 2018 19:57:17 -0700 From: Matthew Wilcox <willy@...radead.org> To: dsterba@...e.cz, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Moving unmaintained filesystems to staging On Wed, Apr 25, 2018 at 10:30:29PM +0200, David Sterba wrote: > I had similar toughts some time ago while browsing the fs/ directory. > Access to the filesystem images can be reimplemented in FUSE, but other > than that, I don't think the in-kernel code would be missed. > > It's hard to know how many users are there. I was curious eg. about bfs, > befs, coda or feevxfs, looked at the last commits and searched around > web if there are any mentions or user community. But as long as there's > somebody listed in MAINTAINERS, the above are not candidates for moving > to staging or deletion. Yeah, it's pretty sad how few commits some of these filesystems have had in recent years. One can argue that they're stable and don't need to be fixed because they aren't broken, but I find it hard to believe that any of them were better-implemented than ext2 which still sees regular bugfixes. As long as there's someone who can be pestered with bugs, I don't see the need to push their baby out of the tree. I'm a bit more nervous about hfsplus; if it has users and no maintainer, those users are at risk. Perhaps we could advertise on Craigslist or something ... maintainer wanted for LTR.
Powered by blists - more mailing lists