diff options
author | Helge Deller <deller@gmx.de> | 2017-07-14 14:49:38 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-07-14 15:05:12 -0700 |
commit | 37511fb5c91db93d8bd6e3f52f86e5a7ff7cfcdf (patch) | |
tree | 2c90b067bcd763a46b9712118bbba0c53285c247 /lib/atomic64_test.c | |
parent | b86faee6d111294fa95a2e89b5f771b2da3c9782 (diff) | |
download | linux-37511fb5c91db93d8bd6e3f52f86e5a7ff7cfcdf.tar.gz linux-37511fb5c91db93d8bd6e3f52f86e5a7ff7cfcdf.tar.bz2 linux-37511fb5c91db93d8bd6e3f52f86e5a7ff7cfcdf.zip |
mm: fix overflow check in expand_upwards()
Jörn Engel noticed that the expand_upwards() function might not return
-ENOMEM in case the requested address is (unsigned long)-PAGE_SIZE and
if the architecture didn't defined TASK_SIZE as multiple of PAGE_SIZE.
Affected architectures are arm, frv, m68k, blackfin, h8300 and xtensa
which all define TASK_SIZE as 0xffffffff, but since none of those have
an upwards-growing stack we currently have no actual issue.
Nevertheless let's fix this just in case any of the architectures with
an upward-growing stack (currently parisc, metag and partly ia64) define
TASK_SIZE similar.
Link: http://lkml.kernel.org/r/20170702192452.GA11868@p100.box
Fixes: bd726c90b6b8 ("Allow stack to grow up to address space limit")
Signed-off-by: Helge Deller <deller@gmx.de>
Reported-by: Jörn Engel <joern@purestorage.com>
Cc: Hugh Dickins <hughd@google.com>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/atomic64_test.c')
0 files changed, 0 insertions, 0 deletions