Re: [PATCH] mm/memory-failure.c: fix memory leak by race between poison and unpoison

2014-05-14 Thread cyc
在 2014-05-14三的 11:21 -0400,Naoya Horiguchi写道: > When a memory error happens on an in-use page or (free and in-use) hugepage, > the victim page is isolated with its refcount set to one. When you try to > unpoison it later, unpoison_memory() calls put_page() for it twice in order to > bring the page

Re: [PATCH] mm/memory-failure.c: fix memory leak by race between poison and unpoison

2014-05-14 Thread Andrew Morton
On Wed, 14 May 2014 11:21:31 -0400 Naoya Horiguchi wrote: > When a memory error happens on an in-use page or (free and in-use) hugepage, > the victim page is isolated with its refcount set to one. When you try to > unpoison it later, unpoison_memory() calls put_page() for it twice in order to >

[PATCH] mm/memory-failure.c: fix memory leak by race between poison and unpoison

2014-05-14 Thread Naoya Horiguchi
When a memory error happens on an in-use page or (free and in-use) hugepage, the victim page is isolated with its refcount set to one. When you try to unpoison it later, unpoison_memory() calls put_page() for it twice in order to bring the page back to free page pool (buddy or free hugepage list.)