From: Greg KH <gregkh@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
jesse.brandeburg@intel.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload
Date: Wed, 15 Oct 2008 15:51:34 -0700 [thread overview]
Message-ID: <20081015225134.GA23026@suse.de> (raw)
In-Reply-To: <alpine.DEB.1.10.0810151843130.19408@gandalf.stny.rr.com>
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
next prev parent reply other threads:[~2008-10-15 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 22:21 [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload Steven Rostedt
2008-10-15 22:46 ` Steven Rostedt
2008-10-15 22:51 ` Greg KH [this message]
2008-10-15 23:01 ` patch disable-config_dynamic_ftrace-due-to-possible-memory-corruption-on-module-unload.patch added to 2.6.27-stable tree gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081015225134.GA23026@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.