public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: apw@shadowen.org, agl@us.ibm.com, mbligh@us.ibm.com,
	linux-kernel@vger.kernel.org, linuxppc64-dev@lists.linuxppc.org
Subject: Re: put_page() tries to handle hugepages but fails
Date: Tue, 27 Apr 2004 15:16:07 +1000	[thread overview]
Message-ID: <20040427051607.GI514@zax> (raw)
In-Reply-To: <20040426221519.3f17c5be.akpm@osdl.org>

On Mon, Apr 26, 2004 at 10:15:19PM -0700, Andrew Morton wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > 1) put_page() can still theoretically call
> >  __page_cache_release() which is wrong (and makes the code misleading)
> 
> Don't think so?
> 
> void put_page(struct page *page)
> {
> 	if (unlikely(PageCompound(page))) {
> 		page = (struct page *)page->private;
> 		if (put_page_testzero(page)) {
> 			void (*dtor)(struct page *page);
> 
> 			dtor = (void (*)(struct page *))page[1].mapping;
> 			(*dtor)(page);
> 		}
> 		return;
> 	}
> 	if (!PageReserved(page) && put_page_testzero(page))
> 		__page_cache_release(page);
> }

Dang.  Missed that patch in the series.  My mistake.

-- 
David Gibson			| For every complex problem there is a
david AT gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

      reply	other threads:[~2004-04-27  5:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23  8:18 put_page() tries to handle hugepages but fails David Gibson
2004-04-23  8:34 ` Andrew Morton
2004-04-23 10:28   ` William Lee Irwin III
2004-04-23 10:35     ` Andrew Morton
2004-04-23 10:47       ` William Lee Irwin III
2004-04-23 11:28         ` William Lee Irwin III
2004-04-27  4:36   ` David Gibson
2004-04-27  4:41     ` David Gibson
2004-04-27  4:47     ` Andrew Morton
2004-04-27  5:05       ` David Gibson
2004-04-27  5:15         ` Andrew Morton
2004-04-27  5:16           ` David Gibson [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=20040427051607.GI514@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=agl@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=mbligh@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox