linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@caldera.de>
To: Art Haas <ahaas@neosoft.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] latest radix-tree pagecache patch and 2.4.19-pre3-ac6
Date: Mon, 25 Mar 2002 19:43:18 +0100	[thread overview]
Message-ID: <20020325194317.A31878@caldera.de> (raw)
In-Reply-To: <20020325114947.A606@debian>; from ahaas@neosoft.com on Mon, Mar 25, 2002 at 11:49:47AM -0600

On Mon, Mar 25, 2002 at 11:49:47AM -0600, Art Haas wrote:
> Hi.
> 
> The original radix-tree patch applies fairly cleanly to the
> -ac6 tree, but there are a few files that need touching up. The
> mm/vmscan.c, mm/filemap.c, and mm/shmem.c files needed the
> most attention. For vmscan.c, a couple of pieces in the original
> patch were dropped, as it looks like they'll only apply (or
> make sense) with the non-rmap code. As for filemap.c, a few
> changes seemed to conflict with the rmap code, so my efforts
> to make a compilable file may have broken the code. But hey,
> I got a `.o' file from the compiler, so it must work, right? :-)

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;


--
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 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 17:49 Art Haas
2002-03-25 18:43 ` Christoph Hellwig [this message]
2002-03-25 22:05   ` Art Haas

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=20020325194317.A31878@caldera.de \
    --to=hch@caldera.de \
    --cc=ahaas@neosoft.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox