From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261694AbVFPAoz (ORCPT ); Wed, 15 Jun 2005 20:44:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261695AbVFPAoz (ORCPT ); Wed, 15 Jun 2005 20:44:55 -0400 Received: from smtp.osdl.org ([65.172.181.4]:6298 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261694AbVFPAow (ORCPT ); Wed, 15 Jun 2005 20:44:52 -0400 Date: Wed, 15 Jun 2005 17:46:35 -0700 (PDT) From: Linus Torvalds To: Bongani Hlope cc: Andrew Morton , ak@muc.de, Kernel Mailing List , Arjan van de Ven , Ingo Molnar Subject: Re: Tracking a bug in x86-64 In-Reply-To: <200506160139.04389.bonganilinux@mweb.co.za> Message-ID: References: <200506132259.22151.bonganilinux@mweb.co.za> <200506160020.21688.bonganilinux@mweb.co.za> <200506160139.04389.bonganilinux@mweb.co.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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