Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp2975158ima; Mon, 22 Oct 2018 20:49:18 -0700 (PDT) X-Google-Smtp-Source: ACcGV62og6AmqpInkT589Fyv4oBASJauxh3aZ8mo3H1EMfeGgMU/D+d5on1llYg6siuYX+zzAMT5 X-Received: by 2002:a63:1066:: with SMTP id 38-v6mr45799593pgq.254.1540266558865; Mon, 22 Oct 2018 20:49:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540266558; cv=none; d=google.com; s=arc-20160816; b=Zj1KMlNN+UARE0EXVDd9V4vZlae1Y0mrJqtM6e4kmZg1lRuiCZthB4CXyGH5ZZk/95 wHORVm8T+NBl/WgP4nEp6DkXo7zKjjH80JF3wAel136kZRCFUCkAVOOQkzI0CIhwRUiB /unhW0EBfwGMAdneNtQfBNsCJhdt+5Mu9pD7m93FUfDT9BkUqftYu/7MUToqdYvc3JE4 HK5X5dDGPwSd4ZzSYsAkfoMXZ8oD5OkgHPL1DfSUCgiB9a3+3Re7SAjeTkoo9AgifqM3 MHrhJxhYY624fLIdhJDPDo3jNTxYzAmxE91QvOrQ27r+CMsGUx2081fuj7rKBBZYRTam elpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=2bS+y9inysE3/A1CGWLrs7GGZfnUT7nmn6owCakDyrA=; b=bJKzDj8QhbI1takStsgmV0tXmDIMORY7HTMptGLsqAraHk9h1x6xb+pkW7iKEqKcl1 dNfPWzma/i2jo9x3kdZaiN3ozevJK4jmLSbyqKRF+MjxviBDWTJwxJS7eVUYj5cMlYMa v2Unom47sswcVnOKeMAvdgCX2UxwuJX7xuz7ymv8IajXHT7xnqRksJghhZX92KULK0/b BgXhncNJ/b+6+3Eqb6dXdqkSIUFNXInlEjdG2zqC/k+8i45AMvTKrVh9nQ0rkig+e7vn 6o4AvcBHhY+GPEIYj6NCFCidFrKKmKCROMgjqOueAl7+vEMnBGt6YT7ZHV9sUfTROFtr vJtA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u11-v6si8720760plr.122.2018.10.22.20.49.03; Mon, 22 Oct 2018 20:49:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727264AbeJWMIr (ORCPT + 99 others); Tue, 23 Oct 2018 08:08:47 -0400 Received: from shells.gnugeneration.com ([66.240.222.126]:51582 "EHLO shells.gnugeneration.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726804AbeJWMIr (ORCPT ); Tue, 23 Oct 2018 08:08:47 -0400 Received: by shells.gnugeneration.com (Postfix, from userid 1000) id 872F41A40245; Mon, 22 Oct 2018 20:47:19 -0700 (PDT) Date: Mon, 22 Oct 2018 20:47:19 -0700 From: Vito Caputo To: linux-kernel Cc: reiserfs-devel@vger.kernel.org Subject: Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too. Message-ID: <20181023034719.tqkvdj2eakh2uh2q@shells.gnugeneration.com> References: <20181022101912.3CE2E292B005@huitzilopochtli.metztli-it.com> <20181023033852.GR32577@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181023033852.GR32577@ZenIV.linux.org.uk> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. That is, assuming it's going to continue to exist in-tree... Regards, Vito Caputo