From: Steven Rostedt <rostedt@goodmis.org>
To: Piotr Haber <phaber@broadcom.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] ftrace: available_filter_functions empty after unloading module
Date: Thu, 13 Dec 2012 08:34:58 -0500 [thread overview]
Message-ID: <1355405698.17101.373.camel@gandalf.local.home> (raw)
In-Reply-To: <50C5CB74.10008@broadcom.com>
On Mon, 2012-12-10 at 12:45 +0100, Piotr Haber wrote:
> > So you unloaded a module that you were tracing, correct? Hmm, the
> > warning that you hit was an accounting error. The accounting of what
> > functions are traced and what isn't. For some reason it tried to disable
> > a function that wasn't being traced.
> Yes, it happens when i unload a module that i traced before
>
> > Can you easily reproduce this? If so, can you give my your .config and
> > the steps you used to trigger it.
> Not 100% but it happens often enough to be annoying
> Attached is the config
> As for reproduction, i load the brcmsmac module, add all it symbols to
> set_ftrace_filter, associate with AP and unload the module
> nothing fancy, i use 'function' tracer
Thanks, I'll see if I can reproduce it.
>
> BTW.
> is it a feature that when there is a traceon trigger added on a function
> from module (like: echo 'brcms_free:traceon' > set_ftrace_filter) after
> module unloading it is not removed?
> just function name gets changed to symbol address
Um, ah, yyyeah! Yeah, yeah, feature. Yep that's a feature alright.
But I think it may be deprecated in the near future.
-- Steve
next prev parent reply other threads:[~2012-12-13 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 14:56 [BUG] ftrace: available_filter_functions empty after unloading module Piotr Haber
2012-12-06 18:10 ` Steven Rostedt
2012-12-07 8:06 ` Piotr Haber
2012-12-07 13:57 ` Steven Rostedt
2012-12-10 11:45 ` Piotr Haber
2012-12-13 13:34 ` Steven Rostedt [this message]
2012-12-13 17:08 ` Steven Rostedt
2012-12-13 19:39 ` Steven Rostedt
2012-12-14 0:05 ` Steven Rostedt
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=1355405698.17101.373.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=phaber@broadcom.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;
as well as URLs for NNTP newsgroup(s).