Hugh Dickins f4cb767d76 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>
2017-06-21 10:56:11 -07:00
..
2017-04-18 20:41:12 +02:00
2017-04-18 20:41:12 +02:00
2017-02-27 18:43:47 -08:00
2017-06-19 21:50:20 +08:00
2015-09-08 15:35:28 -07:00
2017-05-03 15:52:10 -07:00
2015-11-05 19:34:48 -08:00
2017-05-03 15:52:10 -07:00
2017-05-03 15:52:10 -07:00
2016-11-02 10:24:03 -06:00
2016-03-17 15:09:34 -07:00
2017-04-13 18:24:21 -07:00