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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 4 Apr 2022 15:05:11 +0200
From:   Jan Kara <jack@...e.cz>
To:     Pavel Machek <pavel@....cz>
Cc:     Willy Tarreau <w@....eu>, 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?

Hello!

On Mon 04-04-22 12:58:28, Pavel Machek wrote:
> > 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.
> 
> I guess we should start by making sure that distributions don't use it
> by default. Big fat warning + delay is a bit harsh for that, talking
> to them should be enough at this point :-).
> 
> Someone start with Arch Linux ARM.

Yeah, I will write them and CC you. Thanks for notifying me.

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR