From: Edward Shishkin <edward.shishkin@gmail.com>
To: Johannes Buchner <buchner.johannes@gmx.at>
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: reiser4: newbie help needed?
Date: Wed, 02 Dec 2009 10:21:18 +0100 [thread overview]
Message-ID: <4B16318E.7010504@gmail.com> (raw)
In-Reply-To: <20091202192143.48ece851.buchner.johannes@gmx.at>
Johannes Buchner wrote:
> Hi!
>
> I am possibly interested in helping out. Who is currently working on
> reiser4?
Nobody.
Because there is no bugreports.
> I took a look at the TODO lists, are there any simple tasks to
> do for newbies?
>
If you mean the "todo for inclusion", then no.
Reiser4 has only one technical issue. It can
be resolved only by very experienced people.
> Also, where is the latest code development going on?
>
in -mm
> I also believe that on 'sync', reiser4 currently does absolutely
> nothing.
this is not good: a file system should respond on sync (1).
> The comment in reiser4_sync_inodes says reiser4 does its own
> flush elsewhere. Should this be different?
>
you might want to ask such question _before_ sending patches to akpm.
BTW excellent comment, what is not clear?
/**
* reiser4_sync_inodes - sync_inodes of super operations
* @super:
* @wbc:
*
* This method is called by background and non-backgound writeback.
Reiser4's
* implementation uses generic_sync_sb_inodes to call reiser4_writepages for
* each of dirty inodes. Reiser4_writepages handles pages dirtied via shared
* mapping - dirty pages get into atoms. Writeout is called to flush some
* atoms.
*/
Edward.
next prev parent reply other threads:[~2009-12-02 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 6:21 reiser4: newbie help needed? Johannes Buchner
2009-12-02 9:21 ` Edward Shishkin [this message]
2009-12-03 20:25 ` Johannes Buchner
2009-12-04 19:34 ` Edward Shishkin
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=4B16318E.7010504@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=buchner.johannes@gmx.at \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).