mm: PageBuddy and mapcount robustness
Change the _mapcount value indicating PageBuddy from -2 to -128 for more robusteness against page_mapcount() undeflows. Use reset_page_mapcount instead of __ClearPageBuddy in bad_page to ignore the previous retval of PageBuddy(). Signed-off-by: Andrea Arcangeli <aarcange@redhat.com> Reported-by: Hugh Dickins <hughd@google.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
committed by
Linus Torvalds
parent
7b7adc4a01
commit
ef2b4b95a6
@@ -286,7 +286,7 @@ static void bad_page(struct page *page)
|
||||
|
||||
/* Don't complain about poisoned pages */
|
||||
if (PageHWPoison(page)) {
|
||||
__ClearPageBuddy(page);
|
||||
reset_page_mapcount(page); /* remove PageBuddy */
|
||||
return;
|
||||
}
|
||||
|
||||
@@ -317,7 +317,7 @@ static void bad_page(struct page *page)
|
||||
dump_stack();
|
||||
out:
|
||||
/* Leave bad fields for debug, except PageBuddy could make trouble */
|
||||
__ClearPageBuddy(page);
|
||||
reset_page_mapcount(page); /* remove PageBuddy */
|
||||
add_taint(TAINT_BAD_PAGE);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user