From: Alexander Zarochentsev <zam@namesys.com>
To: andrew.j.wade@gmail.com
Cc: reiserfs-list@namesys.com
Subject: Re: [patch] Re: assertion failed: can_hit_entd(ctx, s)
Date: Wed, 30 Aug 2006 10:45:39 +0400 [thread overview]
Message-ID: <200608301045.39978.zam@namesys.com> (raw)
In-Reply-To: <200608291710.06096.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>
Hello,
On 30 August 2006 01:10, Andrew James Wade wrote:
> Hello Alexander,
>
> In addition to your patch, I've also applied the patch below. With
> these two patches the fs is much more stable for me.
That code was removed from reiser4 recently, the patch will be in the
next -mm kernel.
I knew there was a bug somewhere :)
>
> However, something is holding a d_ref across the calls to
> reiser4_writepage. It's not clear to me that this is allowed so my
> patch may not be a full fix.
>
> Andrew Wade
>
> signed-off-by: <andrew.j.wade@gmail.com>
>
> diff -rupN a/fs/reiser4/plugin/item/extent_file_ops.c
> b/fs/reiser4/plugin/item/extent_file_ops.c ---
> a/fs/reiser4/plugin/item/extent_file_ops.c 2006-08-28
> 11:30:33.000000000 -0400 +++
> b/fs/reiser4/plugin/item/extent_file_ops.c 2006-08-29
> 13:06:20.000000000 -0400 @@ -1320,20 +1320,22 @@ static int
> extent_readpage_filler(void * TWIG_LEVEL, CBK_UNIQUE, NULL);
> if (result != CBK_COORD_FOUND) {
> reiser4_unset_hint(hint);
> - return result;
> + goto out;
> }
> ext_coord->valid = 0;
> }
>
> if (zload(ext_coord->coord.node)) {
> reiser4_unset_hint(hint);
> - return RETERR(-EIO);
> + result = RETERR(-EIO);
> + goto out;
> }
> if (!item_is_extent(&ext_coord->coord)) {
> /* tail conversion is running in parallel */
> zrelse(ext_coord->coord.node);
> reiser4_unset_hint(hint);
> - return RETERR(-EIO);
> + result = RETERR(-EIO);
> + goto out;
> }
>
> if (ext_coord->valid == 0)
> @@ -1358,6 +1360,10 @@ static int extent_readpage_filler(void *
> } else
> reiser4_unset_hint(hint);
> zrelse(ext_coord->coord.node);
> +
> +out:
> + /* Calls to this function may be intermingled with VM writeback. */
> + reiser4_txn_restart_current();
> return result;
> }
>
>
> !DSPAM:44f4ad37293861987214747!
Thanks,
Alex.
next prev parent reply other threads:[~2006-08-30 6:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 21:58 Reiser4 stress test Andrew James Wade
2006-08-21 22:41 ` assertion failed: can_hit_entd(ctx, s) Andrew James Wade
2006-08-25 18:42 ` Alexander Zarochentsev
2006-08-26 0:57 ` Andrew James Wade
2006-08-29 21:10 ` [patch] " Andrew James Wade
2006-08-30 6:45 ` Alexander Zarochentsev [this message]
2006-08-30 15:43 ` Hans Reiser
2006-08-30 16:26 ` Alexander Zarochentsev
2006-08-21 22:44 ` assertion failed: JF_ISSET(jprivate(page), JNODE_DIRTY) Andrew James Wade
2006-08-29 21:38 ` Andrew James Wade
2006-08-30 10:26 ` Alexander Zarochentsev
2006-08-30 21:29 ` Andrew James Wade
2006-08-21 23:22 ` assertion failed: keyeq(znode_get_rd_key(node), znode_get_ld_key(node->right)) Andrew James Wade
2006-08-21 23:35 ` [nikita-1936] assertion failed: reiser4_no_counters_are_held() Andrew James Wade
2006-08-25 13:18 ` Alexander Zarochentsev
2006-09-02 0:35 ` [patch] Fix use after free in jrelse_tail Andrew James Wade
2006-08-22 5:23 ` Reiser4 stress test Hans Reiser
2006-08-22 21:57 ` Andrew James Wade
2006-08-22 22:07 ` Andrew James Wade
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=200608301045.39978.zam@namesys.com \
--to=zam@namesys.com \
--cc=andrew.j.wade@gmail.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.