Re: [PATCH] mm: fix new crash in unmapped_area_topdown()

2017-06-21 Thread Michal Hocko
On Tue 20-06-17 02:10:44, Hugh Dickins wrote: > 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

[PATCH] mm: fix new crash in unmapped_area_topdown()

2017-06-20 Thread Hugh Dickins
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 th