From: qiuxishi <qiuxishi@gmail.com>
To: akpm@linux-foundation.org, minchan@kernel.org, lliubbo@gmail.com,
jiang.liu@huawei.com
Cc: mgorman@suse.de, kamezawa.hiroyu@jp.fujitsu.com, mhocko@suse.cz,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
qiuxishi@huawei.com, wujianguo@huawei.com,
bessel.wang@huawei.com, guohanjun@huawei.com,
chenkeping@huawei.com, yinghai@kernel.org, wency@cn.fujitsu.com
Subject: [PATCH] memory-hotplug: fix a drain pcp bug when offline pages
Date: Tue, 21 Aug 2012 20:12:05 +0800 [thread overview]
Message-ID: <50337B15.2090701@gmail.com> (raw)
From: Xishi Qiu <qiuxishi@huawei.com>
When offline a section, we move all the free pages and pcp into MIGRATE_ISOLATE list first.
start_isolate_page_range()
set_migratetype_isolate()
drain_all_pages(),
Here is a problem, it is not sure that pcp will be moved into MIGRATE_ISOLATE list. They may
be moved into MIGRATE_MOVABLE list because page_private() maybe 2. So when finish migrating
pages, the free pages from pcp may be allocated again, and faild in check_pages_isolated().
drain_all_pages()
drain_local_pages()
drain_pages()
free_pcppages_bulk()
__free_one_page(page, zone, 0, page_private(page));
If we add move_freepages_block() after drain_all_pages(), it can not sure that all the pcp
will be moved into MIGRATE_ISOLATE list when the system works on high load. The free pages
which from pcp may immediately be allocated again.
I think the similar bug described in http://marc.info/?t=134250882300003&r=1&w=2
Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
---
mm/page_alloc.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index d0723b2..501f6de 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -673,7 +673,8 @@ static void free_pcppages_bulk(struct zone *zone, int count,
/* must delete as __free_one_page list manipulates */
list_del(&page->lru);
/* MIGRATE_MOVABLE list may include MIGRATE_RESERVEs */
- __free_one_page(page, zone, 0, page_private(page));
+ __free_one_page(page, zone, 0,
+ get_pageblock_migratetype(page));
trace_mm_page_pcpu_drain(page, 0, page_private(page));
} while (--to_free && --batch_free && !list_empty(list));
}
-- 1.7.6.1 .
.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-08-21 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 12:12 qiuxishi [this message]
2012-08-22 3:34 ` [PATCH] memory-hotplug: fix a drain pcp bug when offline pages Minchan Kim
2012-08-22 7:57 ` qiuxishi
2012-08-22 8:14 ` Minchan Kim
2012-08-22 8:30 ` Jiang Liu
2012-08-22 8:37 ` Minchan Kim
2012-08-29 9:35 ` qiuxishi
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=50337B15.2090701@gmail.com \
--to=qiuxishi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bessel.wang@huawei.com \
--cc=chenkeping@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.com \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).