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;
Subject: Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.
To:     Jose R R <jose.r.r@metztli.com>, viro@zeniv.linux.org.uk
Cc:     ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
        linux-kernel <linux-kernel@vger.kernel.org>
References: <20181022101912.3CE2E292B005@huitzilopochtli.metztli-it.com>
 <20181023033852.GR32577@ZenIV.linux.org.uk>
 <CAM12Q5Q5qfrKQrw-2f_PX_FBgFsC6C=dde0gwn8ugBXEx05S_g@mail.gmail.com>
From:   Edward Shishkin <edward.shishkin@gmail.com>
Message-ID: <92ce097a-a896-c346-17e9-4789eb5c3c59@gmail.com>
Date:   Tue, 23 Oct 2018 08:06:07 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAM12Q5Q5qfrKQrw-2f_PX_FBgFsC6C=dde0gwn8ugBXEx05S_g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 10/23/2018 06:28 AM, Jose R R wrote:
> Thank you for replying, Al-
>
> On Mon, Oct 22, 2018 at 8:38 PM Al Viro <viro@zeniv.linux.org.uk> 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).

Hello.

Looks like a regression because of VFS/block-layer changes (I don't test 
new releases carefully enough). Once I am back from vacations, I'll have 
a look at this..

Thanks,
Edward.

> That link you referenced is just my hack for the corresponding Debian
> kernel packaging (wrapper) to build 'Reiser4 the Debian Way', i.e,
> generating reiser4 module & kernel -- suitable for installation media
> -- in addition to Debian'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)...
> This is the actual patch for the Linux 4.14.xy series:
> < https://sourceforge.net/projects/reiser4/files/reiser4-for-linux-4.x/reiser4-for-4.14.1.patch.gz/download
> And yes, Mr. Edward Shishkin, still develops/maintains reiser4, please see:
> < https://github.com/edward6/reiser4 >
>
> I have a couple of reiser4 custom Google Compute Engine (GCE) cloud
> instances which have been running LAMP for a while. One of them runs
> reiser4 -enabled Linux kernel 4.15.x whereas the other one was running
> 4.14.x (both for several months/years already) until I decided to
> upgrade the 4.4.20-1 to newer reiser4 -enabled kernels. By the way
> this last kernel that I installed:
> uname -a
> Linux cohuatl 4.16.0-2+reiser4.0.2-amd64 #1 SMP Debian 4.16.18-2
> (2018-06-27) x86_64 GNU/Linux
>
> seems to be performing nicely --if things continue fine I can assume
> that the drastic change affecting reiser4 hacked kernels occurred
> beginning with upstream Linux series 4.17.x and on...
>
>
> Best Professional Regards.
>