linux-kernel - Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

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]

Message-ID: <20181023041418.GU32577@ZenIV.linux.org.uk>
Date:   Tue, 23 Oct 2018 05:14:18 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     Vito Caputo <vcaputo@...garu.com>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>,
        reiserfs-devel@...r.kernel.org
Subject: Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Mon, Oct 22, 2018 at 09:04:18PM -0700, Vito Caputo wrote:
> > reiser4 has never been in-tree to start with.  And name is completely irrelevant -
> > all I'm refering to is that I have not seen any postings on l-k/fsdevel/etc.
> > from anybody working on that particular out-of-tree codebase.
> > 
> > Put it that way - I would expect the bitrot from (apparent) decade-long
> > inactivity to be a much more serious problem than anything naming-related.
> 
> Would you say bitrot is more or less likely if a project doesn't attract
> fresh meat?

I would say that by now it seems to be a purely academical question - after a while
the bitrot itself is more than enough.  If it's maintained by somebody, take that
question to those somebodies, whoever they are.  I hadn't seen any indications that
it is, and that's literally all I'm trying to comment upon - *IF* it's been
unmaintained, it's almost certainly far past the point of no return due to bitrot.