From: Laurent Riffard <laurent.riffard@free.fr>
To: linux-kernel@vger.kernel.org
Cc: reiserfs-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 6/7] reiser4: writeback_inodes implementation
Date: Sat, 06 Feb 2010 02:07:48 +0100 [thread overview]
Message-ID: <4B6CC0E4.1010105@free.fr> (raw)
In-Reply-To: <201002020256.27208.edward.shishkin@gmail.com>
Hi Edward,
Le 02/02/2010 02:56, Edward Shishkin a écrit :
> . add reiser4 implementation of ->writeback_inodes()
> super operation;
> . cleanup comments.
>
> Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
> ---
> fs/reiser4/context.c | 3 +-
> fs/reiser4/context.h | 2 -
> fs/reiser4/entd.c | 7 ++++--
> fs/reiser4/page_cache.c | 12 +++++------
> fs/reiser4/super_ops.c | 49 +++++++++++++++++++++++++++++-------------------
> fs/reiser4/txnmgr.c | 2 -
> 6 files changed, 45 insertions(+), 30 deletions(-)
>
[...]
>
> Index: linux-2.6.33-rc5-mm1/fs/reiser4/super_ops.c
> ===================================================================
> --- linux-2.6.33-rc5-mm1.orig/fs/reiser4/super_ops.c
> +++ linux-2.6.33-rc5-mm1/fs/reiser4/super_ops.c
> @@ -379,48 +379,59 @@ static void reiser4_clear_inode(struct i
[...]
> -static void reiser4_sync_inodes(struct super_block *super,
> - struct writeback_control *wbc)
> +static int reiser4_writeback_inodes(struct super_block *super,
> + struct bdi_writeback *wb,
> + struct writeback_control *wbc)
> {
> - reiser4_context *ctx;
> + int ret;
> long to_write;
> + reiser4_context *ctx;
>
> if (wbc->for_kupdate)
> /* reiser4 has its own means of periodical write-out */
> - return;
> -
> - to_write = wbc->nr_to_write;
> + goto skip;
> assert("vs-49", wbc->older_than_this == NULL);
>
> + spin_unlock(&inode_lock);
It seems that reiser4 can't be built as a module because of these access to inode_lock...
Kernel: arch/x86/boot/bzImage is ready (#13)
Building modules, stage 2.
MODPOST 188 modules
ERROR: "inode_lock" [fs/reiser4/reiser4.ko] undefined!
make[1]: *** [__modpost] Erreur 1
make: *** [modules] Erreur 2
~~
laurent
prev parent reply other threads:[~2010-02-06 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 1:56 [patch 6/7] reiser4: writeback_inodes implementation Edward Shishkin
2010-02-06 1:07 ` Laurent Riffard [this message]
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=4B6CC0E4.1010105@free.fr \
--to=laurent.riffard@free.fr \
--cc=linux-fsdevel@vger.kernel.org \
--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).