From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3 mmap lack of consistency among runs
Date: Fri, 29 Apr 2005 12:44:45 GMT [thread overview]
Message-ID: <0563I2L12@server5.heliogroup.fr> (raw)
Andrew Morton wrote:
>
> Maybe you're being bitten by the address space randomisation.
>
> Try
> echo 0 > /proc/sys/kernel/randomize_va_space
Ok, it solves my issue, but:
. desabling it through 'echo 0 > /proc/sys/kernel/randomize_va_space' is not
a solution because only the application knows that it wants it to be desabled,
and the application is not root so cannot write to /proc; morever the
application can only speak for itself so desabling should be on a per process
bias.
I can hardly imagine to publish a warning in the README such as:
This software only works if your Linux kernel is configured so that
/proc/sys/kernel/randomize_va_space = 0
. second, my process restart succeeding roughly in 50% cases means that the
randomisation performed is just a toy. A virus assuming fixed memory layout
will still succeed 50% of times to install.
All in all, I'm not concerned about Linux kernel to randomise or not,
but I need to have a reliable way to request a memory region and be granted
that I can request the same one in a futur run.
What is the proper way to get such a memory area ?
next reply other threads:[~2005-04-29 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 12:44 Hubert Tonneau [this message]
2005-04-29 13:20 ` 2.6.12-rc3 mmap lack of consistency among runs Andrew Morton
2005-04-29 13:34 ` Arjan van de Ven
2005-04-29 13:29 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2005-04-29 18:36 Hubert Tonneau
2005-04-29 14:25 Hubert Tonneau
2005-04-28 9:59 Hubert Tonneau
2005-04-29 12:47 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0563I2L12@server5.heliogroup.fr \
--to=hubert.tonneau@fullpliant.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox