From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756143AbYJOWzf (ORCPT ); Wed, 15 Oct 2008 18:55:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753855AbYJOWz0 (ORCPT ); Wed, 15 Oct 2008 18:55:26 -0400 Received: from ns1.suse.de ([195.135.220.2]:50367 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753658AbYJOWz0 (ORCPT ); Wed, 15 Oct 2008 18:55:26 -0400 Date: Wed, 15 Oct 2008 15:51:34 -0700 From: Greg KH To: Steven Rostedt Cc: LKML , stable@kernel.org, Linus Torvalds , Andrew Morton , Arjan van de Ven , jesse.brandeburg@intel.com, Thomas Gleixner , Ingo Molnar Subject: Re: [PATCH -stable] disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on module unload Message-ID: <20081015225134.GA23026@suse.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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