mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Greg KH <gregkh@suse.de>
Cc: Roland Dreier <rdreier@cisco.com>,
	Matt Fleming <matt@console-pimps.org>,
	David Kiliani <mail@davidkiliani.de>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: drivers/staging/meilhaus build broken with ftrace
Date: Thu, 6 Aug 2009 18:51:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0908061849260.2840@gandalf.stny.rr.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908061844300.2840@gandalf.stny.rr.com>

On Thu, 6 Aug 2009, Steven Rostedt wrote:
> Yes the module did something funky, but what broke recordmcount.pl was not 
> something that is not allowed. The code broke because a weak function was 
> the only function in a section. This patch keeps it from crashing.
> 
> Hmm, maybe I should make it warn, because a weak function by itself in a 
> section will not be traced.

Now the question is, is this a crucial enough change to push for 31, or 
should we leave this for 32?

This patch is small enough for 31, but to add a warning would require a 
little more code rework. I can queue this up for 31 and then have the 
warning ready for 32.

-- Steve
> 
> diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
> index d29baa2..979da4b 100755
> --- a/scripts/recordmcount.pl
> +++ b/scripts/recordmcount.pl
> @@ -393,7 +393,7 @@ while (<IN>) {
>  	    $read_function = 0;
>  	}
>  	# print out any recorded offsets
> -	update_funcs() if ($text_found);
> +	update_funcs() if (defined($ref_func));
>  
>  	# reset all markers and arrays
>  	$text_found = 0;
> @@ -441,7 +441,7 @@ while (<IN>) {
>  }
>  
>  # dump out anymore offsets that may have been found
> -update_funcs() if ($text_found);
> +update_funcs() if (defined($ref_func));
>  
>  # If we did not find any mcount callers, we are done (do nothing).
>  if (!$opened) {
> 

  reply	other threads:[~2009-08-06 22:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 21:37 Roland Dreier
2009-08-06 21:46 ` Steven Rostedt
2009-08-06 22:29   ` Greg KH
2009-08-06 22:47     ` Steven Rostedt
2009-08-06 22:51       ` Steven Rostedt [this message]
2009-08-06 22:58         ` Roland Dreier
2009-08-06 23:32           ` Greg KH
2009-08-07  0:01             ` [GIT PULL][2.6.31] tracing: have recordmcount.pl handle a section with only weak functions Steven Rostedt
2009-08-07  6:50               ` Ingo Molnar

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=alpine.DEB.2.00.0908061849260.2840@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@davidkiliani.de \
    --cc=matt@console-pimps.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    /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

all inboxes | Powered by JetHome®