All of lore.kernel.org
 help / color / mirror / Atom feed
From: Art Haas <ahaas@neosoft.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] latest radix-tree pagecache patch and 2.4.19-pre3-ac6
Date: Mon, 25 Mar 2002 16:05:51 -0600	[thread overview]
Message-ID: <20020325160551.B1424@debian> (raw)
In-Reply-To: <20020325194317.A31878@caldera.de>

On Mon, Mar 25, 2002 at 07:43:18PM +0100, Christoph Hellwig wrote:
>
> [ ... my comments ... ]
> 
> I think I have found at least once obvious bug:
> 
>  a) this cannot actually compile, pagecache_lock is gone..
>  b) find_get_page already does locking internally AND also
>     grabs a reference to the page.
> 
> This should probably be just a radix_tree_lookup()
> 
> @@ -1064,7 +999,7 @@
>  	spin_lock(&pagemap_lru_lock);
>  	while (--index >= start) {
>  		spin_lock(&pagecache_lock);
> -		page = __find_page(mapping, index);
> +		page = find_get_page(mapping, index);
>  		spin_unlock(&pagecache_lock);
>  		if (!page || !PageActive(page))
>  			break;
> 

The file does compile, and my kernel running now does have
the changes I've made. I must be picking up the variable
from somewhere else, and I can't say where that is right
now. Hmmmm ....

Thanks for looking over the patch. I'll make the change
and try things out. Thanks again for working on the radix-tree
patches!

-- 
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
 -- Benjamin Franklin, Historical Review of Pennsylvania, 1759
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

      reply	other threads:[~2002-03-25 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 17:49 [PATCH] latest radix-tree pagecache patch and 2.4.19-pre3-ac6 Art Haas
2002-03-25 18:43 ` Christoph Hellwig
2002-03-25 22:05   ` Art Haas [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=20020325160551.B1424@debian \
    --to=ahaas@neosoft.com \
    --cc=hch@caldera.de \
    --cc=linux-mm@kvack.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 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.