Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756490AbYBVKfb (ORCPT ); Fri, 22 Feb 2008 05:35:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762471AbYBVKfO (ORCPT ); Fri, 22 Feb 2008 05:35:14 -0500 Received: from namei.org ([69.55.235.186]:56219 "EHLO us.intercode.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753475AbYBVKfN (ORCPT ); Fri, 22 Feb 2008 05:35:13 -0500 Date: Fri, 22 Feb 2008 21:33:52 +1100 (EST) From: James Morris X-X-Sender: jmorris@us.intercode.com.au To: Ingo Molnar cc: Sam Ravnborg , Linus Torvalds , linux-kernel@vger.kernel.org, Arjan van de Ven , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" Subject: Re: Regression [Was: Boot hang with stack protector on x86_64] In-Reply-To: <20080222093621.GG327@elte.hu> Message-ID: References: <20080222075950.GB2660@uranus.ravnborg.org> <20080222093621.GG327@elte.hu> 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: 1023 Lines: 35 On Fri, 22 Feb 2008, Ingo Molnar wrote: > > * Sam Ravnborg wrote: > > > > This is on an x86_64 system (actually an Intel SDV -- so it might be > > > "special"). > > > > This is a regression. Can you please revert this commit. We can redo > > it wehn the -fstack-protector stuff are properly fixed in x86. > > No! > > James, could you please check whether x86.git#testing: > > http://people.redhat.com/mingo/x86.git/README > > works fine for you? That has all the current stackprotector fixes. I > plan to send a separate pull request with just the stackprotector fixes > to Linus, they are looking good in testing so far. Nope, same problem. (I followed your instructions in the readme exactly). - James -- James Morris -- 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/