From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: Jonathan Briggs <jbriggs@esoft.com>
Subject: Re: Is as_ops.c releasepage patch still needed?
Date: Tue, 29 Aug 2006 10:01:53 +0400 [thread overview]
Message-ID: <200608291001.53573.zam@namesys.com> (raw)
In-Reply-To: <1156186198.10806.5.camel@localhost>
Hi,
On 21 August 2006 22:49, Jonathan Briggs wrote:
> The following patch was posted to the Reiser4 list August 3 by zam.
> Is it still needed? It solved many problems for me, making my
> systems able to actually complete full Beagle indexing.
the patch submitted already and will be included into the next -mm
kernel (after 2.6.18-rc4-mm3).
>
> But I have not seen this patch show up in the last two mm kernel
> releases. Did something else fix it or is this patch still needed?
>
>
> Index: linux-2.6-git/fs/reiser4/as_ops.c
> ===================================================================
> --- linux-2.6-git.orig/fs/reiser4/as_ops.c
> +++ linux-2.6-git/fs/reiser4/as_ops.c
> @@ -350,6 +350,11 @@ int reiser4_releasepage(struct page *pag
> if (PageDirty(page))
> return 0;
>
> + /* extra page reference is used by reiser4 to protect
> + * jnode<->page link from this ->releasepage(). */
> + if (page_count(page) > 3)
> + return 0;
> +
> /* releasable() needs jnode lock, because it looks at the
> jnode fields * and we need jload_lock here to avoid races with
> jload(). */ spin_lock_jnode(node);
--
Alex.
prev parent reply other threads:[~2006-08-29 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 18:49 Is as_ops.c releasepage patch still needed? Jonathan Briggs
2006-08-29 6:01 ` Alexander Zarochentsev [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=200608291001.53573.zam@namesys.com \
--to=zam@namesys.com \
--cc=jbriggs@esoft.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.