Commit: 400737bf7a8dcc0c84bf7b01d5637db6db0e1678 
Author: Adrian Bunk <bunk@kernel.org> Sun, 28 Oct 2007 22:33:36 +0100 

    Linux 2.6.16.56-rc2

Commit: 63419d8efa745ed9a9b7e91a324b9b933dfdbb34 
Author: Hugh Dickins <hugh@veritas.com> Sun, 28 Oct 2007 22:32:04 +0100 

    hugetlb: fix size=4G parsing
    
    On 32-bit machines, mount -t hugetlbfs -o size=4G gave a 0GB filesystem,
    size=5G gave a 1GB filesystem etc: there's no point in masking size with
    HPAGE_MASK just before shifting its lower bits away, and since HPAGE_MASK is a
    UL, that removed all the higher bits of the unsigned long long size.
    
    Signed-off-by: Hugh Dickins <hugh@veritas.com>
    Signed-off-by: Adrian Bunk <bunk@kernel.org>

Commit: 255189a700d809000157d5eed1a3ede9e6426f68 
Author: Hugh Dickins <hugh@veritas.com> Sun, 28 Oct 2007 22:22:25 +0100 

    hugetlb: fix error return for brk() entering a hugepage region
    
    The lats commit causes the wrong return value.
    is_hugepage_only_range() is a boolean, so we should return
    -EINVAL rather than 1.
    
    Also - we can use "mm" instead of looking up "current->mm" again.
    
    Signed-off-by: Hugh Dickins <hugh@veritas.com>
    Signed-off-by: Adrian Bunk <bunk@kernel.org>

Commit: 6a93b22bc8569315b2e0ce07297b73673882925a 
Author: David Gibson <david@gibson.dropbear.id.au> Sun, 28 Oct 2007 22:20:34 +0100 

    hugetlb: check for brk() entering a hugepage region
    
    Unlike mmap(), the codepath for brk() creates a vma without first checking
    that it doesn't touch a region exclusively reserved for hugepages.  On
    powerpc, this can allow it to create a normal page vma in a hugepage
    region, causing oopses and other badness.
    
    Add a test to prevent this.  With this patch, brk() will simply fail if it
    attempts to move the break into a hugepage reserved region.
    
    Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
    Signed-off-by: Adrian Bunk <bunk@kernel.org>

Commit: 42ea9d4b9da1bb26d519f91c9464fd093c7a56a2 
Author: Ken Chen <kenneth.w.chen@intel.com> Sun, 28 Oct 2007 21:40:41 +0100 

    [IA64] fix ia64 is_hugepage_only_range
    
    fix is_hugepage_only_range() definition to be "overlaps"
    instead of "within architectural restricted hugetlb address
    range".  Simplify the ia64 specific code that used to use
    is_hugepage_only_range() to just check which region the
    address is in.
    
    Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Adrian Bunk <bunk@kernel.org>