Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763580AbYCEVol (ORCPT ); Wed, 5 Mar 2008 16:44:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761810AbYCEVng (ORCPT ); Wed, 5 Mar 2008 16:43:36 -0500 Received: from mail.suse.de ([195.135.220.2]:40042 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763193AbYCEVne (ORCPT ); Wed, 5 Mar 2008 16:43:34 -0500 Date: Wed, 5 Mar 2008 22:43:33 +0100 (CET) From: Michael Matz To: Joe Buck Cc: Jan Hubicka , Aurelien Jarno , "H. Peter Anvin" , linux-kernel@vger.kernel.org, gcc@gcc.gnu.org Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag In-Reply-To: <20080305212005.GC17267@synopsys.com> Message-ID: References: <20080305153020.GA24631@volta.aurel32.net> <47CEC3AA.6080709@zytor.com> <20080305195834.GA17267@synopsys.com> <20080305202319.GA17053@volta.aurel32.net> <20080305204234.GB17267@synopsys.com> <20080305204945.GB14011@atrey.karlin.mff.cuni.cz> <20080305212005.GC17267@synopsys.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1516 Lines: 41 Hi, On Wed, 5 Mar 2008, Joe Buck wrote: > > > On Wed, 5 Mar 2008, Jan Hubicka wrote: > > > Linux kernel is disabling red zone and use kernel code model, yet the > > > ABI is not going to be adjusted for that. > > > > > > This is resonably easy to fix on kernel side in signal handling, or by > > > removing std usage completely > > On Wed, Mar 05, 2008 at 10:02:07PM +0100, Michael Matz wrote: > > That is true. But it requires updating the kernel to a fixed one if you > > want to run your programs compiled by 4.3 :-/ Not something we'd like to > > demand. > > I changed the title just for emphasis. > > I think that we can't ship 4.3.0 if signal handlers on x86/x86_64 > platforms for both Linux and BSD systems will mysteriously (to the users) > fail, and it doesn't matter whose fault it is. FWIW I don't think it's a release blocker for 4.3.0. The error is arcane and happens seldomly if at all. And only on unfixed kernels. A program needs to do std explicitely, which most don't do _and_ get hit by a signal while begin in a std region. This happens so seldom that it didn't occur in building the next openSuSE 11.0, and it continually builds packages with 4.3 since months. It should be worked around in 4.3.1 if at all. Ciao, Michael. -- 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/