From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758813AbZCRQyY (ORCPT ); Wed, 18 Mar 2009 12:54:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755092AbZCRQyQ (ORCPT ); Wed, 18 Mar 2009 12:54:16 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:55956 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754358AbZCRQyP (ORCPT ); Wed, 18 Mar 2009 12:54:15 -0400 Date: Wed, 18 Mar 2009 17:54:07 +0100 From: Ingo Molnar To: Jaswinder Singh Rajput Cc: Steven Rostedt , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Peter Zijlstra , x86 maintainers , LKML Subject: Re: oops in tracepoint_update_probe_range() (was: Re: [oops -tip] : x86 AMD 64) Message-ID: <20090318165407.GA921@elte.hu> References: <1237393396.3322.6.camel@localhost.localdomain> <20090318163531.GE21331@elte.hu> <1237394936.3132.1.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1237394936.3132.1.camel@localhost.localdomain> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jaswinder Singh Rajput wrote: > On Wed, 2009-03-18 at 17:35 +0100, Ingo Molnar wrote: > > * Jaswinder Singh Rajput wrote: > > > > > Good: f4c3c4cdb1de232 > > > Bad : 1e08816af0bc345 > > > > > > Config: > > > http://userweb.kernel.org/~jaswinder/oops_20090318/config-hpdv5-tip-bad-20090318 > > > > > > oops: > > > http://userweb.kernel.org/~jaswinder/oops_20090318/oops_page1.jpg > > > http://userweb.kernel.org/~jaswinder/oops_20090318/oops_page2.jpg > > > http://userweb.kernel.org/~jaswinder/oops_20090318/oops_page3.jpg > > > http://userweb.kernel.org/~jaswinder/oops_20090318/oops_page4.jpg > > > > > > > > > > Steve, Frederic - the crashes above are in: > > > > tracepoint_update_probe_range() > > > > in a modular kernel apparently. > > > > This fixed the oops for me, Is this looks OK to you: > > Subject: [PATCH] x86: tracepoint.c fix oops > > BUG: unable to handle kernel NULL pointer dereference at (null) > IP: [] tracepoint_update_probe_range+0x1f/0x9b > PGD 13d5fb067 PUD 13d688067 PMD 0 > Oops: 0000 [#1] SMP > > Signed-off-by: Jaswinder Singh Rajput > --- > kernel/tracepoint.c | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c > index 7960274..80d1353 100644 > --- a/kernel/tracepoint.c > +++ b/kernel/tracepoint.c > @@ -280,6 +280,8 @@ void tracepoint_update_probe_range(struct tracepoint *begin, > > mutex_lock(&tracepoints_mutex); > for (iter = begin; iter < end; iter++) { > + if (!iter) > + goto out; > mark_entry = get_tracepoint(iter->name); > if (mark_entry) { > set_tracepoint(&mark_entry, iter, > @@ -288,6 +290,7 @@ void tracepoint_update_probe_range(struct tracepoint *begin, > disable_tracepoint(iter); > } > } > +out: > mutex_unlock(&tracepoints_mutex); hm, that does not look right - how can 'iter' become zero? It's a text-ish symbol. I think what we might have here is a corruption of the tracepoint data structures. Ingo