diff options
author | Hugh Dickins <hughd@google.com> | 2017-06-20 02:10:44 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-06-21 10:56:11 -0700 |
commit | f4cb767d76cf7ee72f97dd76f6cfa6c76a5edc89 (patch) | |
tree | 425524affe25e84c5d1efbf1c5785f3c2c2cce33 /Makefile | |
parent | 9705596d08ac87c18aee32cc97f2783b7d14624e (diff) | |
download | linux-f4cb767d76cf7ee72f97dd76f6cfa6c76a5edc89.tar.bz2 |
mm: fix new crash in unmapped_area_topdown()
Trinity gets kernel BUG at mm/mmap.c:1963! in about 3 minutes of
mmap testing. That's the VM_BUG_ON(gap_end < gap_start) at the
end of unmapped_area_topdown(). Linus points out how MAP_FIXED
(which does not have to respect our stack guard gap intentions)
could result in gap_end below gap_start there. Fix that, and
the similar case in its alternative, unmapped_area().
Cc: stable@vger.kernel.org
Fixes: 1be7107fbe18 ("mm: larger stack guard gap, between vmas")
Reported-by: Dave Jones <davej@codemonkey.org.uk>
Debugged-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Hugh Dickins <hughd@google.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions