From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 6 Mar 2002 10:21:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 6 Mar 2002 10:21:27 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:39951 "EHLO atrey.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id ; Wed, 6 Mar 2002 10:21:10 -0500 Date: Wed, 6 Mar 2002 16:21:06 +0100 From: Pavel Machek To: "Richard B. Johnson" Cc: kernel list , torvalds@transmeta.com, "Marcelo W. Tosatti" Subject: Re: execve() fails to report errors Message-ID: <20020306152106.GD21479@atrey.karlin.mff.cuni.cz> In-Reply-To: <20020305233437.GA130@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > Take this trivial .c program. Obviously correct. > > > > > > struct foo { > > char fill[1*1024*1024*1024]; > > }; > > > > struct foo a; > > > > void > > main(void) > > { > > } > > > > Compile. Run. Segfault. > > > > Whose fault? Kernels; it fails to corectly report not enough address > > space. > > I think the bug has to be found earlier on up the food chain. > If you do: Well, nothing earlier can know if there will be enough address space at runtime. (It depends on kernel config .. 3GB vs 2GB ...) Pavel -- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic.