linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: users@nilfs.org, linux-fsdevel@vger.kernel.org, ryusuke@osrg.net
Subject: Re: Deadlock with nilfs on 2.6.31.4
Date: Mon, 2 Nov 2009 22:32:45 +0100	[thread overview]
Message-ID: <20091102223245.1840d8fd@neptune.home> (raw)
In-Reply-To: <20091103.020502.126745214.ryusuke@osrg.net>

Hi Ryusuke Konishi,

On Tue, 03 November 2009 Ryusuke Konishi wrote:
> I found the cause of the hang issue reported on ARM targets.
> The following patch would fix the issue.
> 
> It resolved hang problem on my Feroceon based Linux box.
> 
> Could you try if the patch fixes the hang of yours ?
> 
> Thanks,
> Ryusuke Konishi

Seems to fix the issue here as well, at least collectd now does write
its data to the RRD files as well as to the remote system, no frozen
process yet for 2 and a half hours uptime.

Thanks for the fix,
Bruno

Tested-by: Bruno Prémont <bonbons@linux-vserver.org>
> --
> From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
> 
> nilfs2: fix dirty page accounting leak causing hang at write
> 
> Some users experienced a consistent hang while using NILFS on
> ARM-based targets.
> 
> I found this was caused by an underflow of dirty pages counter.  A
> b-tree cache routine was marking page dirty without adjusting page
> account information.
> 
> This fixes the dirty page accounting leak and resolves the hang on
> arm-based targets.
> 
> Reported-by: Bruno Premont <bonbons@linux-vserver.org>
> Reported-by: Dunphy, Bill <WDunphy@tandbergdata.com>
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
> ---
>  fs/nilfs2/btnode.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nilfs2/btnode.c b/fs/nilfs2/btnode.c
> index 5941958..435864c 100644
> --- a/fs/nilfs2/btnode.c
> +++ b/fs/nilfs2/btnode.c
> @@ -276,8 +276,7 @@ void nilfs_btnode_commit_change_key(struct
> address_space *btnc, "invalid oldkey %lld (newkey=%lld)",
>  				       (unsigned long long)oldkey,
>  				       (unsigned long long)newkey);
> -		if (!test_set_buffer_dirty(obh) &&
> TestSetPageDirty(opage))
> -			BUG();
> +		nilfs_btnode_mark_dirty(obh);
>  
>  		spin_lock_irq(&btnc->tree_lock);
>  		radix_tree_delete(&btnc->page_tree, oldkey);
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-11-02 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 18:38 Deadlock with nilfs on 2.6.31.4 Bruno Prémont
2009-10-22 17:51 ` Ryusuke Konishi
2009-10-22 20:19   ` Bruno Prémont
2009-11-02 17:05     ` Ryusuke Konishi
2009-11-02 21:32       ` Bruno Prémont [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=20091102223245.1840d8fd@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ryusuke@osrg.net \
    --cc=users@nilfs.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).