powerpc/mm/radix: Use mm->task_size for boundary checking instead of addr_limit
authorAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Thu, 13 Apr 2017 19:18:21 +0000 (00:48 +0530)
committerMichael Ellerman <mpe@ellerman.id.au>
Wed, 19 Apr 2017 10:00:18 +0000 (20:00 +1000)
commitbe77e999e3937322b7e15274b8fc7da309a040a0
treee850b22d9ee7ae37a8e5b8ceb6f16fad8ae1b7e3
parent8d1b48ef580097e111c2644e6fc6041b9784d218
powerpc/mm/radix: Use mm->task_size for boundary checking instead of addr_limit

We don't init addr_limit correctly for 32 bit applications. So default to using
mm->task_size for boundary condition checking. We use addr_limit to only control
free space search. This makes sure that we do the right thing with 32 bit
applications.

We should consolidate the usage of TASK_SIZE/mm->task_size and
mm->context.addr_limit later.

This partially reverts commit fbfef9027c2a7ad (powerpc/mm: Switch some
TASK_SIZE checks to use mm_context addr_limit).

Fixes: fbfef9027c2a ("powerpc/mm: Switch some TASK_SIZE checks to use mm_context addr_limit")
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/mm/hugetlbpage-radix.c
arch/powerpc/mm/mmap.c
arch/powerpc/mm/slice.c
arch/powerpc/mm/subpage-prot.c