Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932793AbXBXNeD (ORCPT ); Sat, 24 Feb 2007 08:34:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932223AbXBXNeD (ORCPT ); Sat, 24 Feb 2007 08:34:03 -0500 Received: from 69-100-st.zelcom.ru ([80.92.100.69]:1789 "EHLO etherstorm.feelingofgreen.ru" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932793AbXBXNeB (ORCPT ); Sat, 24 Feb 2007 08:34:01 -0500 Date: Sat, 24 Feb 2007 16:33:53 +0300 Message-ID: <87irdrbry6.wl@betelheise.deep.net> From: Samium Gromoff <_deepfire@feelingofgreen.ru> To: Florian Weimer Cc: Samium Gromoff <_deepfire@feelingofgreen.ru>, Kyle Moffett , David Wagner , LKML Kernel Subject: Re: [PATCH] Undo some of the pseudo-security madness In-Reply-To: <87k5y799lo.fsf@mid.deneb.enyo.de> References: <87r6toufpp.wl@betelheise.deep.net> <1D317613-B0B6-4517-81B5-DBF3978FA413@mac.com> <87lkjvvnc6.wl@betelheise.deep.net> <87k5y799lo.fsf@mid.deneb.enyo.de> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/23.0.51 (i486-pc-linux-gnu) MULE/5.0 (SAKAKI) X-Face: "P-:w!.&Hdk.h~~pT`!Q%H6;/8Cce^m&%vIn"W-SXb4h88dCgwD\_}N5:\}lowY2gxg0u^wVO*L\$C@MvBDRTmh/=,468w{W{OTc$kfq5O9Y!`pd+N}SMHrN+Gs>jXe5}}EL`cRbc0^_0cZ-}M\b~55I;Qe$1uL8M`M`82<_%CQ(GwLk."M>zBLn:-u>n,$kjH`~Uo[pH`08#\G!GVMd`%7![m9]*w5PMts4@m>=;lX41Z90N MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1030 Lines: 31 At Sat, 24 Feb 2007 10:40:51 +0100, Florian Weimer wrote: > > * Samium Gromoff: > > > Lisp environments can produce standalone executables > > If you've got a stand-alone executable, you don't need MAP_FIXED. The > ELF loader maps the program at a fixed address anyway (at least on > i386 and x86_64, I haven't checked others). Not so. The thing is that the picture is of two pieces: - the executable - the unrelocatable lisp core (which is unrelocatable by the virtue of non-PIC code) which is mapped into the AS of the executable. It is the latter which breaks, as its map can overlap with randomized pieces of the executable (along with its libraries). > AFAIK, PolyML has recently made the switch to stand-alone executables > for this reason. regards, Samium Gromoff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/