From: John Richard Moser <nigelenki@comcast.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.16.16 Parameter-controlled mmap/stack randomization
Date: Mon, 22 May 2006 21:34:31 -0400 [thread overview]
Message-ID: <447266A7.8080100@comcast.net> (raw)
In-Reply-To: <1148346316.3100.6.camel@laptopd505.fenrus.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arjan van de Ven wrote:
> On Mon, 2006-05-22 at 12:31 -0400, John Richard Moser wrote:
>> It is still possible that ARCH_STACK_RANDOM_BITS_DEFAULT breaks things.
>> The current kernel default broke emacs at first I heard;
>
> hearsay.. where did you hear this and what exact randomization was this?
>
Sorry, I googled it, you were talking about brk() randomization (which I
STILL want to see! :D)
http://lkml.org/lkml/2005/1/28/29
>
>> I believe we
>> started with 64KiB of stack randomization and then upped it to 8MiB when
>> emacs was fixed.
>
> this is new information to me, I find this really really hard to believe
> as true but maybe you have information I don't have...
See this is why I said "I believe..." :)
>
>
>
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRHJmpQs1xW0HCTEFAQLX9Q//Rm0CvdLkPSq0UCLot9Mqyuj4REVwaGrV
VwJOGJgElyE/RFqu5MI8ab8CV7WUgKiV/wWrxyrfXRpW4uuYbedIsXAw8tzlJq/c
o+4FLVQBS+cXJ96VXIsHLIConlF21pXBZDzBFHHwfSsUsmbvgeJ0WavC3x3N7y6B
Bq4/RfVmf6yEECGSemoApzpbMR01anK6/nc1t0P9iMpsK5tlE9Q7r4/pB3wyRVmY
66GKAbcC4gU9CHtuu2e158/FCQXcfVZ1nFvKWGZyPWGAZAEiGazrMM5iv962EHX3
bqHKcMhr6BxsQt6LG7jzplg6YMDppqqWtiiIUfVJSnW65k1a2AmdGAEi0ZIe7IDm
T/YJRJqi54NOcI+UJ4FcODdlxfZ2EiVXNY22sf9wpn1lQpWt1TX4pbsaHjHVlLB7
8pBQzHSD+P9rDJ0eXfAC+0Vi0V/K1Yna/qhtdEnX2pp08zc2rdC6hu466MGWsH1u
vzD4772nWekd/c9Yby2BXbq+lwXHNA5iIwLBPA/NQwmSENFCdYhIFSrIOBjctQ1W
u85q3dhtFfXhTdwRdjfYtpoiYGIDx4l0wUohHPNLh5sD7NC81EtDOHm/WZfx2C1G
NAWsWkDPntxUpUcuSm+3nl3zDoPYPSMRiztwbWvm0BEdpn2uDyO0v5fMWdenpvMN
sn7wkuMaTlQ=
=OLQP
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-23 1:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 1:00 [PATCH] 2.6.16.16 Parameter-controlled mmap/stack randomization John Richard Moser
2006-05-20 3:36 ` John Richard Moser
2006-05-20 5:23 ` John Richard Moser
2006-05-20 13:47 ` Arjan van de Ven
2006-05-20 15:23 ` John Richard Moser
2006-05-22 1:06 ` Pavel Machek
2006-05-22 2:46 ` John Richard Moser
2006-05-22 8:33 ` Pavel Machek
2006-05-22 16:31 ` John Richard Moser
2006-05-22 17:00 ` Pavel Machek
2006-05-22 17:54 ` John Richard Moser
2006-05-22 18:40 ` Pavel Machek
2006-05-22 19:02 ` John Richard Moser
2006-05-22 19:12 ` Pavel Machek
2006-05-22 19:27 ` John Richard Moser
2006-05-22 19:41 ` Pavel Machek
2006-05-22 20:05 ` John Richard Moser
2006-05-23 1:05 ` Arjan van de Ven
2006-05-23 1:34 ` John Richard Moser [this message]
2006-05-20 17:13 ` John Richard Moser
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=447266A7.8080100@comcast.net \
--to=nigelenki@comcast.net \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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