Re: Is it time to remove reiserfs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

On Sun 20-02-22 12:13:04, Matthew Wilcox wrote:
> Keeping reiserfs in the tree has certain costs.  For example, I would
> very much like to remove the 'flags' argument to ->write_begin.  We have
> the infrastructure in place to handle AOP_FLAG_NOFS differently, but
> AOP_FLAG_CONT_EXPAND is still around, used only by reiserfs.
> 
> Looking over the patches to reiserfs over the past couple of years, there
> are fixes for a few syzbot reports and treewide changes.  There don't
> seem to be any fixes for user-spotted bugs since 2019.  Does reiserfs
> still have a large install base that is just very happy with an old
> stable filesystem?  Or have all its users migrated to new and exciting
> filesystems with active feature development?
> 
> We've removed support for senescent filesystems before (ext, xiafs), so
> it's not unprecedented.  But while I have a clear idea of the benefits to
> other developers of removing reiserfs, I don't have enough information to
> weigh the costs to users.  Maybe they're happy with having 5.15 support
> for their reiserfs filesystems and can migrate to another filesystem
> before they upgrade their kernel after 5.15.
> 
> Another possibility beyond outright removal would be to trim the kernel
> code down to read-only support for reiserfs.  Most of the quirks of
> reiserfs have to do with write support, so this could be a useful way
> forward.  Again, I don't have a clear picture of how people actually
> use reiserfs, so I don't know whether it is useful or not.
> 
> NB: Please don't discuss the personalities involved.  This is purely a
> "we have old code using old APIs" discussion.

So from my distro experience installed userbase of reiserfs is pretty small
and shrinking. We still do build reiserfs in openSUSE / SLES kernels but
for enterprise offerings it is unsupported (for like 3-4 years) and the module
is not in the default kernel rpm anymore.

So clearly the filesystem is on the deprecation path, the question is
whether it is far enough to remove it from the kernel completely. Maybe
time to start deprecation by printing warnings when reiserfs gets mounted
and then if nobody yells for year or two, we'll go ahead and remove it?

								Honza
-- 
Jan Kara <jack@xxxxxxxx>
SUSE Labs, CR



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux