diff options
| author | Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> | 2017-04-14 00:48:21 +0530 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-04-19 20:00:18 +1000 |
| commit | be77e999e3937322b7e15274b8fc7da309a040a0 (patch) | |
| tree | e850b22d9ee7ae37a8e5b8ceb6f16fad8ae1b7e3 /crypto/anubis.c | |
| parent | 8d1b48ef580097e111c2644e6fc6041b9784d218 (diff) | |
| download | linux-stable-be77e999e3937322b7e15274b8fc7da309a040a0.tar.gz linux-stable-be77e999e3937322b7e15274b8fc7da309a040a0.tar.bz2 linux-stable-be77e999e3937322b7e15274b8fc7da309a040a0.zip | |
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>
Diffstat (limited to 'crypto/anubis.c')
0 files changed, 0 insertions, 0 deletions