Re: Reiser4 Upstream Git Repositories on GitHub

[Edward Shishkin <edward.shishkin@gmail.com>]

On 09/27/2016 03:43 AM, Ivan Shapovalov wrote:
> On 2016-09-27 at 00:37 +0200, Edward Shishkin wrote:
>> On 09/27/2016 12:05 AM, Ivan Shapovalov wrote:
>>> On 2016-09-24 at 22:16 +0200, Edward Shishkin wrote:
>>>> Hello everyone,
>>>>
>>>> I have set up the updated Namesys repositories at my Github page.
>>>> Those repositories are supposed to contain the latest updates in
>>>> the (stable) master branch and in other (experimental) branches
>>>> that
>>>> I'll announce.
>>>>
>>>> 1)https://github.com/edward6/reiser4
>>>>
>>>> This is a "standalone" reiser4 tree, which doesn't include
>>>> specific
>>>> changes of Linux kernel needed for reiser4 port. Such changes can
>>>> be
>>>> found at the project's page on Sourceforge:
>>>> https://sourceforge.net/projects/reiser4/
>>>>
>>>> An example of work with the standalone reiser4 tree:
>>>>
>>>> . Patch the respective kernel with the latest available stuff
>>>> from
>>>>      Sourceforge;
>>>> . cd to the "fs" directory;
>>>> . delete the directory reiser4;
>>>> . instead of the deleted stuff clone the standalone reiser4
>>>>      repository from Github;
>>>> . build and install as usual.
>>>>
>>>> 2) Libaal and Reiser4progs:
>>>>
>>>> https://github.com/edward6/libaal
>>>> https://github.com/edward6/reiser4progs
>>>>
>>>> Before building Libaal and Reiser4progs execute the ./prepare
>>>> script,
>>>> which will create files needed for build process.
>>>>
>>>> Thanks,
>>>> Edward.
>>> Wow, finally.
>>>
>>> Maybe we could avoid that "all changes for 10 years" commit?
>> Hi Ivan,
>> Sorry, don't have a time to granulate it.
>>
>>> I tried to keep track of all patches since 3.2...
>> There will be "all changes for 6 years" commit.
>> Is it much better?
> I've noticed that your tree has an if(0) in should_punch_hole(),
> while you've previously posted code for race detection in the hole
> punch mechanism, and this code is not in your tree... is this correct?

Yes, I disabled hole punching because of specific problems:
if the flush procedure can not find a parent of a dirty child
in the tree, then it jumps to error path and reports about
corruption.

If dirty page cluster contains only zeros, then hole punching
code kills its parent item (the idea of hole punching is that a
set of zeros is represented by nothing on disk). Thus, we need
to teach the flush code to handle that situation (absence of
parent) properly.

Unfortunately I exceeded time limits allocated for flush
modifications, so that task went to long-term TODO..

Edward.