Re: 2.6.12-rc3 mmap lack of consistency among runs

[Andrew Morton <akpm@osdl.org>]

Hubert Tonneau <hubert.tonneau@fullpliant.org> wrote:
>
> As a way to freeze then restart processes,
> the first shot of the process calls 'mmap' with NULL as 'start',
> then restarts of the process will call 'mmap' with the value received at the
> first shot, and expect to be assigned the requested area.
> 
> This used to work perfectly with 2.6.11 and all previous kernels (unless some
> shared libraries have been upgraded in the mean time),
> but with 2.6.12-rc3 (I have not tested rc1 and rc2) it fails half time.
> 
> I can solve the problem through specifying a 'start' value at the first shot,
> but then I will get a more serious problem on the long run because the
> application would then have to be awared of the general layout of the address
> space enforced by the kernel and so could be disturbed by any change.

Maybe you're being bitten by the address space randomisation.

Try
	echo 0 > /proc/sys/kernel/randomize_va_space
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/