• A
    mm: handle initialising compound pages at orders greater than MAX_ORDER · 6babc32c
    Andy Whitcroft 提交于
    When we initialise a compound page we initialise the page flags and head
    page pointer for all base pages spanned by that page.  When we initialise
    a gigantic page (a page of order greater than or equal to MAX_ORDER) we
    have to initialise more than MAX_ORDER_NR_PAGES pages.  Currently we
    assume that all elements of the mem_map in this page are contigious in
    memory.  However this is only guarenteed out to MAX_ORDER_NR_PAGES pages,
    and with SPARSEMEM enabled they will not be contigious.  This leads us to
    walk off the end of the first section and scribble on everything which
    follows, BAD.
    
    When we reach a MAX_ORDER_NR_PAGES boundary we much locate the next
    section of the mem_map.  As gigantic pages can only be maximally aligned
    we know this will occur at exact multiple of MAX_ORDER_NR_PAGES pages from
    the start of the page.
    
    This is a bug fix for the gigantic page support in hugetlbfs.
    
    Credit to Mel Gorman for spotting the issue.
    Signed-off-by: NAndy Whitcroft <apw@shadowen.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Cc: Jon Tollefson <kniht@linux.vnet.ibm.com>
    Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
    Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
    6babc32c
page_alloc.c 128.4 KB