public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	jaswinderrajput@gmail.com, fweisbec@gmail.com,
	rostedt@goodmis.org, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:tracing/ftrace] tracepoints: dont update zero-sized tracepoint sections
Date: Wed, 18 Mar 2009 18:57:28 GMT	[thread overview]
Message-ID: <tip-ec625cb29e66824f7ce41082617aeb93fa4e42e2@git.kernel.org> (raw)
In-Reply-To: <1237394936.3132.1.camel@localhost.localdomain>

Commit-ID:  ec625cb29e66824f7ce41082617aeb93fa4e42e2
Gitweb:     http://git.kernel.org/tip/ec625cb29e66824f7ce41082617aeb93fa4e42e2
Author:     Ingo Molnar <mingo@elte.hu>
AuthorDate: Wed, 18 Mar 2009 19:54:04 +0100
Commit:     Ingo Molnar <mingo@elte.hu>
CommitDate: Wed, 18 Mar 2009 19:55:00 +0100

tracepoints: dont update zero-sized tracepoint sections

Zero-sized tracepoint sections can occur if tracing is enabled but
no tracepoint is defined. Do not emit a warning in that case.

Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
LKML-Reference: <1237394936.3132.1.camel@localhost.localdomain>
Signed-off-by: Ingo Molnar <mingo@elte.hu>


---
 kernel/tracepoint.c |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
index adf2873..1ef5d3a 100644
--- a/kernel/tracepoint.c
+++ b/kernel/tracepoint.c
@@ -278,10 +278,8 @@ tracepoint_update_probe_range(struct tracepoint *begin, struct tracepoint *end)
 	struct tracepoint *iter;
 	struct tracepoint_entry *mark_entry;
 
-	if (!begin) {
-		WARN_ON_ONCE(1);
+	if (!begin)
 		return;
-	}
 
 	mutex_lock(&tracepoints_mutex);
 	for (iter = begin; iter < end; iter++) {

  parent reply	other threads:[~2009-03-18 18:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 16:23 [oops -tip] : x86 AMD 64 Jaswinder Singh Rajput
2009-03-18 16:35 ` oops in tracepoint_update_probe_range() (was: Re: [oops -tip] : x86 AMD 64) Ingo Molnar
2009-03-18 16:41   ` Frederic Weisbecker
2009-03-18 16:48   ` Jaswinder Singh Rajput
2009-03-18 16:54     ` Ingo Molnar
2009-03-18 16:56     ` Frederic Weisbecker
2009-03-18 17:27       ` Ingo Molnar
2009-03-18 17:33         ` Frederic Weisbecker
2009-03-18 17:33     ` [tip:tracing/ftrace] tracing: fix oops in tracepoint_update_probe_range() Jaswinder Singh Rajput
2009-03-18 17:38       ` Jaswinder Singh Rajput
2009-03-18 17:52         ` Jaswinder Singh Rajput
2009-03-18 17:51     ` Jaswinder Singh Rajput
2009-03-18 17:56       ` Jaswinder Singh Rajput
2009-03-18 18:00         ` Frederic Weisbecker
2009-03-18 18:12           ` Jaswinder Singh Rajput
2009-03-18 19:35             ` Frederic Weisbecker
2009-03-18 18:58         ` Ingo Molnar
2009-03-18 19:04           ` Jaswinder Singh Rajput
2009-03-18 17:57     ` Jaswinder Singh Rajput
2009-03-18 18:57     ` Ingo Molnar [this message]
2009-03-19  7:18   ` Lai Jiangshan
2009-03-19  7:46     ` Ingo Molnar
2009-03-19  9:41       ` Jaswinder Singh Rajput
2009-03-19 13:22       ` Mathieu Desnoyers
2009-03-19 13:34         ` Steven Rostedt
2009-03-19 14:03           ` Mathieu Desnoyers
2009-03-19 15:50           ` Ingo Molnar
2009-03-19 16:00             ` Mathieu Desnoyers
2009-03-19 16:20               ` Steven Rostedt
2009-03-23  5:18                 ` Rusty Russell
2009-03-19 15:42         ` Jaswinder Singh Rajput

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=tip-ec625cb29e66824f7ce41082617aeb93fa4e42e2@git.kernel.org \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jaswinderrajput@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox