[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081015225134.GA23026@suse.de>
Date: Wed, 15 Oct 2008 15:51:34 -0700
From: Greg KH <gregkh@...e.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>, stable@...nel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>,
jesse.brandeburg@...el.com, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possible
memory corruption on module unload
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists