Re: 2.5.63 accesses below %esp (was: Re: ntfs OOPS (2.5.63))
Arjan van de Ven (email@example.com)
Wed, 12 Mar 2003 15:24:57 +0000
On Wed, Mar 12, 2003 at 07:20:39AM -0800, Linus Torvalds wrote:
> 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.
I know. And when the gcc bug was found (and fixed)
we audited the disassembly of sched.o for this and it
didn't get triggered by this bug.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/