From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: Chris Ross <chris@tebibyte.org>
Cc: Andrew Morton <akpm@osdl.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, kernel@kolivas.org
Subject: Re: Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause
Date: Sat, 30 Oct 2004 18:53:32 +0900 [thread overview]
Message-ID: <4183649C.7070601@jp.fujitsu.com> (raw)
In-Reply-To: <41835F4D.2060508@tebibyte.org>
Chris Ross wrote:
>
>
> Hiroyuki KAMEZAWA escreveu:
>
>> zone->free_area[order]->nr_free is corrupted, this patch fix it.
>>
>> It looks there is no area->nr_free++ code during freeing pages, now.
>
>
> It's corrupt because area is out of scope at that point - it's declared
> within the for loop above.
>
> Should I move your fix into the loop or move the declaration of area to
> function scope?
>
Oh, Okay, my patch was wrong ;(.
Very sorry for wrong hack.
This one will be Okay.
Sorry,
Kame <kamezawa.hiroyu@jp.fujitsu.com>
-
linux-2.6.10-rc1-mm2-kamezawa/mm/page_alloc.c | 1 +
1 files changed, 1 insertion(+)
diff -puN mm/page_alloc.c~cleanup2 mm/page_alloc.c
--- linux-2.6.10-rc1-mm2/mm/page_alloc.c~cleanup2 2004-10-30 18:40:19.024529640 +0900
+++ linux-2.6.10-rc1-mm2-kamezawa/mm/page_alloc.c 2004-10-30 18:40:40.225306632 +0900
@@ -262,6 +262,7 @@ static inline void __free_pages_bulk (st
coalesced = base + page_idx;
set_page_order(coalesced, order);
list_add(&coalesced->lru, &zone->free_area[order].free_list);
+ zone->free_area[order].nr_free++;
}
static inline void free_pages_check(const char *function, struct page *page)
_
next prev parent reply other threads:[~2004-10-30 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0410251823230.21539-100000@chimarrao.boston.redhat.com>
2004-10-25 22:33 ` Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause Rik van Riel
2004-10-28 12:06 ` Marcelo Tosatti
2004-10-28 15:27 ` Chris Ross
2004-10-28 15:01 ` Marcelo Tosatti
2004-10-29 13:36 ` Chris Ross
2004-10-29 14:46 ` Chris Ross
2004-10-30 8:25 ` Hiroyuki KAMEZAWA
2004-10-30 8:45 ` Chris Ross
2004-10-30 8:58 ` Hiroyuki KAMEZAWA
2004-10-30 9:30 ` Chris Ross
2004-10-30 9:53 ` Hiroyuki KAMEZAWA [this message]
2004-10-30 10:42 ` Thomas Gleixner
2004-10-31 12:33 ` Thomas Gleixner
2004-10-30 15:38 ` Chris Ross
2004-10-29 15:09 ` Thomas Gleixner
2004-10-23 12:59 Javier Marcet
2004-10-23 19:33 ` Andrew Morton
2004-10-23 23:03 ` Con Kolivas
2004-10-25 21:51 ` Rik van Riel
2004-10-25 22:13 ` Andrew Morton
2004-10-26 8:01 ` Nick Piggin
2004-10-29 22:39 ` Thomas Gleixner
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=4183649C.7070601@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=chris@tebibyte.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).