From: Al Viro <viro@ZenIV.linux.org.uk>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.
Date: Tue, 23 Oct 2018 04:54:25 +0100 [thread overview]
Message-ID: <20181023035425.GS32577@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20181023034719.tqkvdj2eakh2uh2q@shells.gnugeneration.com>
On Mon, Oct 22, 2018 at 08:47:19PM -0700, Vito Caputo wrote:
> On Tue, Oct 23, 2018 at 04:38:52AM +0100, Al Viro wrote:
> > On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology wrote:
> > > I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the prior hung reiser4 -patched kernel 4.18.15-1 in the Google Compute Engine (GCE) cloud instance. After less than 24 hours the 4.17.19-1 hung in similar way to the 4.18.15-1.
> > >
> > > Please note that I had been running my custom Metztli Reiser4 Debian Stretch image with reiser4 linux 4.14.20-1 without issues for several months
> > > < https://github.com/Metztli/reiser4-debian-kernel-packaging-4.14.20 > --until I decided to upgrade to newer kernel(s).
> >
> > Er... Does anybody maintain reiser4 these days? I can't recall a single mail
> > along the lines of "such-and-such VFS/VM/scheduler/etc. change would break reiser4"
> > in quite a few years (more than a decade, most likely)...
>
> I've wondered if we should rename reiserfs to something else. As-is,
> it's not likely to attract any developers since it may as well be named
> hitlerfs or something similarly uncomfortable to explain to a
> significant other as what you've been working on.
Sigh... Godwin Law in action, at the third posting in thread ;-/
> That is, assuming it's going to continue to exist in-tree...
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.
next prev parent reply other threads:[~2018-10-23 3:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 10:19 Metztli Information Technology
2018-10-23 3:38 ` Al Viro
2018-10-23 3:47 ` Vito Caputo
2018-10-23 3:54 ` Al Viro [this message]
2018-10-23 4:04 ` Vito Caputo
2018-10-23 4:14 ` Al Viro
2018-10-23 4:28 ` Jose R R
2018-10-23 6:06 ` Edward Shishkin
2019-01-29 13:54 Metztli Information Technology
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181023035425.GS32577@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vcaputo@pengaru.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®