From: Linus Torvalds <torvalds@osdl.org>
To: Bongani Hlope <bonganilinux@mweb.co.za>
Cc: Andrew Morton <akpm@osdl.org>,
ak@muc.de, Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Tracking a bug in x86-64
Date: Wed, 15 Jun 2005 17:46:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0506151740110.8487@ppc970.osdl.org> (raw)
In-Reply-To: <200506160139.04389.bonganilinux@mweb.co.za>
On Thu, 16 Jun 2005, Bongani Hlope wrote:
>
> I just tested, 2.6.12-rc6 minus randomisation-top-of-stack-randomization.patch Works For Me (tm)
Ok, that _should_ mean that plain -rc6 should work fine for you, if you do
echo 0 > /proc/sys/kernel/randomize_va_space
and it would be good to validate that. But it still leaves the question of
exactly _why_ that stack randomization matters for you.. Very strange.
Arjan, Ingo, any ideas? The code looks "Obviously Correct(tm)", but maybe
there's something missing. Does it get the rlimit case wrong?
Bongani, what does a simple
cat /proc/self/maps
say for you with randomization enabled? Is there something mapped close to
the stack segment..
(It would be even better to see that for one of the processes that tends
to core-dump, like "cc1", but that would require you to catch it, probably
by doign ^Z at just the right time)
Linus
next prev parent reply other threads:[~2005-06-16 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 20:59 Bongani Hlope
2005-06-13 21:23 ` Andi Kleen
2005-06-13 21:39 ` Bongani Hlope
2005-06-13 21:48 ` Andi Kleen
2005-06-14 15:36 ` Linus Torvalds
2005-06-14 20:27 ` Andrew Morton
2005-06-14 21:19 ` Bongani Hlope
2005-06-15 22:20 ` Bongani Hlope
2005-06-15 22:39 ` Linus Torvalds
2005-06-15 23:39 ` Bongani Hlope
2005-06-16 0:46 ` Linus Torvalds [this message]
2005-06-16 2:02 ` Andi Kleen
2005-06-16 6:49 ` Bongani Hlope
[not found] ` <xfkll4lfy41.fsf@uxkm53.drewag.de>
2005-07-05 19:52 ` Bongani Hlope
2005-07-05 21:12 ` Andrew Morton
2005-07-06 6:34 ` Arjan van de Ven
2005-07-06 18:20 ` Bongani Hlope
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=Pine.LNX.4.58.0506151740110.8487@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bonganilinux@mweb.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®