Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261874AbVDETYu (ORCPT ); Tue, 5 Apr 2005 15:24:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261954AbVDETVY (ORCPT ); Tue, 5 Apr 2005 15:21:24 -0400 Received: from fire.osdl.org ([65.172.181.4]:18366 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261898AbVDETSA (ORCPT ); Tue, 5 Apr 2005 15:18:00 -0400 Date: Tue, 5 Apr 2005 12:19:50 -0700 (PDT) From: Linus Torvalds To: Stas Sergeev cc: Ingo Molnar , linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: crash in entry.S restore_all, 2.6.12-rc2, x86, PAGEALLOC In-Reply-To: <4252E2C9.9040809@aknet.ru> Message-ID: References: <20050405065544.GA21360@elte.hu> <4252E2C9.9040809@aknet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 856 Lines: 24 On Tue, 5 Apr 2005, Stas Sergeev wrote: > > Attached is a quick fix, which I'll be > testing to death tomorrow at work. This one can pass through vm86 mode stuff without the high-16-bit fixup, as far as I can tell. Also, I think your optimization to optimistically load SS is valid per se, but we need to find out how some kernel thread gets zero stack associated with it. They should all have the full "struct pt_reg" as far as I could see, which means that we should never be _so_ high up the stack that SS/ESP would be on the next page. So I'd actually prefer to get that mystery explained.. Linus - 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/