linux-kernel - Re: Is it time to remove reiserfs?

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, 4 Apr 2022 12:18:02 +0200
From:   Willy Tarreau <w@....eu>
To:     Pavel Machek <pavel@....cz>
Cc:     Jan Kara <jack@...e.cz>, Matthew Wilcox <willy@...radead.org>,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        reiserfs-devel@...r.kernel.org
Subject: Re: Is it time to remove reiserfs?

Hi Pavel,

On Mon, Apr 04, 2022 at 12:07:32PM +0200, Pavel Machek wrote:
> > Well, if someone uses Reiserfs they better either migrate to some other
> > filesystem or start maintaining it. It is as simple as that because
> > currently there's nobody willing to invest resources in it for quite a few
> > years and so it is just a question of time before it starts eating people's
> > data (probably it already does in some cornercases, as an example there are
> > quite some syzbot reports for it)...
> 
> Yes people should migrate away from Reiserfs. I guess someone should
> break the news to Arch Linux ARM people.
> 
> But I believe userbase is bigger than you think and it will not be
> possible to remove reiserfs anytime soon.

I was about to say the opposite until I noticed that one of my main
dev machine has its kernel git dir on it because it's an old FS from
a previous instance of this machine before an upgrade and it turns out
that this FS still had lots of available space to store git trees :-/

So maybe you're right and there are still a bit more than expected out
there. However I really think that most users who still have one are in
the same situation as I am, they're not aware of it. So aside big fat
warnings at mount time (possibly with an extra delay), there's nothing
that will make that situation change.

At the very least disabling it by default in Kconfig and in distros
should be effective. I really don't think that there are still users
who regularly update their system and who have it on their rootfs, but
still having data on it, yes, possibly. The earlier they're warned,
the better.

At least now I know I need to migrate this FS.

Regards,
Willy