Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 12 Mar 2003 10:12:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 12 Mar 2003 10:12:01 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:51214 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Wed, 12 Mar 2003 10:12:00 -0500 Date: Wed, 12 Mar 2003 07:20:39 -0800 (PST) From: Linus Torvalds To: Arjan van de Ven cc: Szakacsits Szabolcs , Subject: Re: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63)) In-Reply-To: <1047464392.1556.4.camel@laptop.fenrus.com> Message-ID: 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: 868 Lines: 26 On 12 Mar 2003, Arjan van de Ven wrote: > > and all vendors always ship -fno-frame-pointer kernels so far so those > users are ok! Until recently there was no way to build a non > -fno-frame-pointer kernel! Not entirely true. Even with the traditional -fomit-frame-pointer build, "sched.c" has always been built with -fno-fomit-frame-pointer in order to get the correct "wchan" of callers of schedule() and wait_on(). See kernel/Makefile for details. So yes, old kernels (and CONFIG_FRAME_POINTER=n) have traditionally avoided the bug _mostly_. But it could still bite us in some rather important functions. 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/