Re: [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possiblememory corruption on module unload
From: Greg KH
Date: Wed Oct 15 2008 - 18:55:36 EST
On Wed, Oct 15, 2008 at 06:46:12PM -0400, Steven Rostedt wrote:
>
> On Wed, 15 Oct 2008, Steven Rostedt wrote:
> >
> > The problem arises when we trace functions and modules are unloaded.
>
> Note, it is not just module unloading. The issue can happen when the
> init functions of a module are freed and the nvram is vmapped there as
> well.
Ok, that makes sense why so many people hit this.
I'll go do a 2.6.27.1 with this patch in it right now, thanks for
spending the time to look into this.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/