linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Piotr Haber" <phaber@broadcom.com>
To: "Steven Rostedt" <rostedt@goodmis.org>,
	"Frederic Weisbecker" <fweisbec@gmail.com>,
	"Ingo Molnar" <mingo@redhat.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: [BUG] ftrace: available_filter_functions empty after unloading module
Date: Thu, 6 Dec 2012 15:56:54 +0100	[thread overview]
Message-ID: <50C0B236.4090200@broadcom.com> (raw)

Hi,
not sure if this is a bug or just my misuse of ftrace.
I get this warring after unloading a module that i traced before (used
function tracer and 'brcmsmac*' as filter in set_ftrace_filter).
After that reading available_filter_functions gives "No such device".

Regards
Piotr

------------[ cut here ]------------
WARNING: at kernel/trace/ftrace.c:1564
__ftrace_hash_rec_update.part.34+0x20d/0x250()
Hardware name: Latitude E6420
Modules linked in: brcmsmac(O) brcmutil(O) bcma(O) mac80211(O)
cfg80211(O) rfkill(O) arc4 cordic fuse ip6table_filter ip6_tables
ebtable_nat ebtables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state
nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle iptable_filter
ip_tables bridge stp llc snd_hda_codec_hdmi snd_hda_codec_idt coretemp
kvm_intel snd_hda_intel kvm snd_hda_codec nouveau ttm drm_kms_helper drm
ghash_clmulni_intel aesni_intel snd_hwdep snd_pcm_oss snd_mixer_oss
snd_pcm ablk_helper snd_seq_dummy snd_seq_oss i2c_algo_bit i2c_core
mxm_wmi cryptd lrw pl2303 usbserial snd_seq_midi aes_x86_64 snd_rawmidi
xts snd_seq_midi_event gf128mul snd_seq video snd_timer ppdev
dell_laptop dell_wmi serio_raw sparse_keymap dcdbas snd_seq_device snd
microcode lpc_ich mfd_core parport_pc wmi soundcore snd_page_alloc lp
parport ipv6 ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom
crc32c_intel ahci libahci sdhci_pci sdhci mmc_core e1000e [last
unloaded: rfkill]
Pid: 2498, comm: bash Tainted: G           O 3.7.0-rc8 #3
Call Trace:
 [<ffffffff810574ff>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105755a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff810fdd7d>] __ftrace_hash_rec_update.part.34+0x20d/0x250
 [<ffffffff810fea15>] ftrace_hash_move+0x1c5/0x1e0
 [<ffffffff81100388>] ftrace_regex_release+0x98/0x150
 [<ffffffff8118f7ac>] __fput+0xcc/0x290
 [<ffffffff8118f97e>] ____fput+0xe/0x10
 [<ffffffff810798e7>] task_work_run+0xa7/0xe0
 [<ffffffff81015a64>] do_notify_resume+0x74/0x80
 [<ffffffff81289eee>] ? trace_hardirqs_on_thunk+0x3a/0x3f
 [<ffffffff8157ed12>] int_signal+0x12/0x17
---[ end trace 476f7270ba7905df ]---


             reply	other threads:[~2012-12-06 14:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 14:56 Piotr Haber [this message]
2012-12-06 18:10 ` [BUG] ftrace: available_filter_functions empty after unloading module 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
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=50C0B236.4090200@broadcom.com \
    --to=phaber@broadcom.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    /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).