From owner-freebsd-stable@FreeBSD.ORG Thu Oct 8 18:05:28 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 488BC106568D; Thu, 8 Oct 2009 18:05:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1F1708FC0C; Thu, 8 Oct 2009 18:05:28 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 7B08C46B0C; Thu, 8 Oct 2009 14:05:27 -0400 (EDT) Date: Thu, 8 Oct 2009 19:05:27 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Daniel Eischen In-Reply-To: Message-ID: References: <20091007200959.3c93904f.lehmann@ans-netz.de> <20091008062326.11720.qmail@avocado.salatschuessel.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: jhell , "freebsd-stable@freebsd.org" , Oliver Lehmann Subject: Re: samba - SIGABRT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Oct 2009 18:05:28 -0000 On Thu, 8 Oct 2009, Daniel Eischen wrote: >> While it's probably a bug that the Samba port compiles --pie, it's also a >> bug that our linking bits aren't handling PIE properly either. The goal is >> to fix PIE with the non-NULL mapping feature in the immediate future, so >> with any luck the abort message won't matter too much longer. > > How about reverting this change or defaulting security.bsd.map_at_zero=1 > until either ports can handle this properly or our -pie is fixed, and we've > had at least a release with pre-built packages that don't have the problem? Sorry, I should have been more clear: the problem is with run-time linking, not compile-time linking. Kostik has just posted patches for the run-time linker to current@, which should allow the existing binaries to work with map_at_zero=0. If we aren't able to get the run-time linker fixes into 8.0, we will definitely revert the default change for map_at_zero so that it is enabled. However, since there is a significant security benefit to shipping with map_at_zero disabled, I think we should try hard to ship 8.0 with a fixed rtld. Robert