Re: reiser4 patches and todo list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 01/05/2012 08:33 PM, Marcin Baczyński wrote:
2012/1/5 Edward Shishkin<edward.shishkin@xxxxxxxxx>:
On 01/05/2012 11:51 AM, doiggl@xxxxxxxxxxxxxxxxxx wrote:

- Are there any plans for a reiser4 patch for Linux kernel 3.2/3.1/3.0
series ?

Maybe for 3.2, but not sure..

fs-writeback has been changed a lot and I don't have a time to adjust
reiser4 to every stupid VFS change. Anybody care to? I'll provide the

Well, if you have patience to provide the hints for somebody with little
kernel experience and who is just learning how the internals of VFS
work than I think I can do it :]

Ok, I think that adjusting reiser4 to 3.2 would be a good start.

Unlike other file systems reiser4's ->writepages() address space
operation doesn't actually write pages to disk. Instead
reiser4_writepages() puts them into a transaction (actually it
takes place for so-called "anonymous" pages, dirtied via mmap).

So with every portion of writeback-ed inodes we also need in addition
to call reiser4_writeout().

Such slight inconsistency with VFS semantic was fixed via introducing
a new super operation ->writeback_inodes(), so that reiser4_writeback_inodes() makes sure that everything is written
properly (see patches 0-7 for details):

The following 6 patches adjusts reiser4 to further changes in

And now (in 3.1) fs-writeback.c got changed again. Specifically,
semantic of writeback_sb_inodes(), the "implicit" ->writeback_inodes()
super operation, has been changed: now it writes not necessarily all
inodes of a superblock. As a result It'll break reiser4_sync_fs() and
reiser4's entd worker semantic, which require _all_ inodes of reiser4
superblock to be writeback-ed.

So I guess we need a version of writeback_sb_inodes(), which writes (optionally) _all_ inodes of a superblock.

Note, that fs-writeback is a single pain in the ass: in other bits
reiser4 is perfectly coherent with VFS.

BTW is there any chance that R4 will be merged into Linus' tree?

Merging upstream has mostly marketing/political aspects which would
mean additional burden for me personally.

Who cares to merge it with upstream? It might be important for some
vendor, who is ready to pay money for reiser4 development.

Perhaps we'll consider possibility of merging, but not now.
Now, when I spend my weekends for reiser4, I would prefer to
concentrate on scientific aspects of file system development.


Or that known bugs will get fixed? Following this list, one can get an
impression that R4 is in a maintenance-only mode...

- Has the reiser4 todo list changed since 2009 [1] ?


Thanks Glenn
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Linux BTRFS]     [Linux NFS]     [Linux Filesystems]     [Ext4 Filesystem]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux