lkml.org 
[lkml]   [2017]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [criu] 1M guard page ruined restore
On Tue, Jun 20, 2017 at 12:51:16PM +0200, Oleg Nesterov wrote:
>
> You can write a simple test. Just do mmap(MAP_GROWSDOWN) and look at
> /proc/self/maps. If it reports vm_start + PAGE_SIZE rather than addr
> returned by mmap, then the kernel is old.
>
> > Second I guess we might need to detect @stack_guard_gap runtime as
> > well
>
> I do not think so. criu does not need to know about the new guard area
> at all. It simply doesn't exist from user-space pov.
>
> In fact, I think this should have been true even before this change, just
> stack_guard_page_start() was not accurate and this is the reason (I guess)
> you had to play with stack guard; the first page (hidden by show_map_vma)
> can have a valid stack data, for example if the application played with
> MAP_FIXED or munmap().
>
> So I think you should simply disable, say, unmap_guard_pages() and most
> of all other MAP_GROWSDOWN code in criu.

Looks like a good plan. Thanks Oleg! Gonna try it.

Cyrill

\
 
 \ /
  Last update: 2017-06-20 13:10    [W:0.118 / U:4.832 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site