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:47:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908061844300.2840@gandalf.stny.rr.com> (raw)
In-Reply-To: <20090806222906.GA14792@suse.de>
On Thu, 6 Aug 2009, Greg KH wrote:
> On Thu, Aug 06, 2009 at 05:46:57PM -0400, Steven Rostedt wrote:
> >
> > Hi Roland,
> >
> > On Thu, 6 Aug 2009, Roland Dreier wrote:
> >
> > > Commit fc4c7355 ("ftrace: Fix the conditional that updates $ref_func")
> > > breaks the build of drivers/staging/meilhaus with ftrace enabled:
> > >
> > > CC [M] drivers/staging/meilhaus/me0600_device.o
> > > No function to reference at scripts/recordmcount.pl line 339, <IN> line 258.
> > > make[4]: *** [drivers/staging/meilhaus/me0600_device.o] Error 9
> > >
> > > Yes, that's crazy, but the situation is the following:
> > >
> > > - for some reason I can't fathom, the meilhaus driver declares
> > > me0600_pci_constructor() as weak in drivers/staging/meilhaus/me0600_device.h
> > >
> > > - me0600_pci_constructor() is the only function in .text in
> > > drivers/staging/meilhaus/me0600_device.c
> > >
> > > so recordmcount.pl ends up finding only one weak function in .text, and
> > > so it never sets $ref_func before calling update_funcs().
> >
> > Ug, I figured this would happen. I think I have a patch somewhere that can
> > handle this.
>
> Don't make ftrace do a lot of work if it's a bug in the staging driver.
> Odds are the code in there should be fixed instead, I'll gladly take a
> patch to do that.
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.
-- 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) {
next prev parent reply other threads:[~2009-08-06 22:47 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 [this message]
2009-08-06 22:51 ` Steven Rostedt
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.0908061844300.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®