From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751191AbWGBRH2 (ORCPT ); Sun, 2 Jul 2006 13:07:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751287AbWGBRH2 (ORCPT ); Sun, 2 Jul 2006 13:07:28 -0400 Received: from py-out-1112.google.com ([64.233.166.180]:24867 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1751191AbWGBRH1 (ORCPT ); Sun, 2 Jul 2006 13:07:27 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ps4JikX0o0NXcGJj8XwLb/fU4IdMdzNvDoSB1P917/TG/A+1Dx0pkzHi74B+7qBbTyljvhTn4WKaTq5Naw262aFJ3ufBF2QudtWVYLs7pjM44w2iMPz4+NDb4/SRPw+24FLR4hOnN9JQ5u++ltR1kSlpyp0Qen2XNJEkUimz9WQ= Message-ID: Date: Sun, 2 Jul 2006 10:07:27 -0700 From: "Miles Lane" To: "Arjan van de Ven" Subject: Re: 2.6.17-mm5 -- Busted toolchain? -- usr/klibc/exec_l.c:59: undefined reference to `__stack_chk_fail' Cc: "Andrew Morton" , LKML In-Reply-To: <1151826131.3111.5.camel@laptopd505.fenrus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1151788673.3195.58.camel@laptopd505.fenrus.org> <1151789342.3195.60.camel@laptopd505.fenrus.org> <1151826131.3111.5.camel@laptopd505.fenrus.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/2/06, Arjan van de Ven wrote: > > > https://wiki.ubuntu.com/GccSsp > > > > It appears that Ubuntu's Edgy Eft (the development tree) now contains > > "Stack Smashing Protection" enabled by default. I found a web page > > that states that -fno-stack-protector can be used to disable this > > functionality. Interestingly, another web page stated that SSP has > > been enabled in Redhat compilers for a long time and is now also > > enabled in Debian SID. Perhaps -fno-stack-protector should be added > > to the kernel build be default? > > > gcc 4.1 and later have this feature yes. > HOWEVER the gcc people were not stupid, they did not force this on > people, they require you to put -fstack-protector on the commandline. > Debian and RH/Fedora do this. > If Ubuntu patched gcc rather than just putting it in the build > environment... then you should switch to a less braindead distribution > really ;) > or at least ask them to fix this. Well, from the web page referenced at the top of this message, you can see that they are already aware of these issues: Cons: * It breaks current upstream kernel builds and potentially other direct usages of gcc. Kernel is by far the most important use case. Upstream should change the default options to build with -fno-stack-protector by default. * It is not conformant to upstream gcc behaviour. You can reach the key people who are working on this for Ubuntu here: Matt Zimmerman -- mdz at ubuntu dot com Martin Pitt -- martin.pitt at ubuntu dot com Perhaps you can convince them to back out this functional change? Does this mean that you don't want to see these fno-stack-protector patches go into Andrew's tree? Miles