From: Gleb Natapov <gleb@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: module unloading hangs after using ftrace with 3.11.0-rc1
Date: Sun, 21 Jul 2013 14:52:16 +0300 [thread overview]
Message-ID: <20130721115215.GG20379@redhat.com> (raw)
Hi Steven,
After tracing KVM using trace-cmd with kvm trace points enables I tried
to unload kvm modules and rmmod hanged in tracing_reset_all_online_cpus:
[ 1234.665038] rmmod D 00000000ffffffff 0 7819 7664 0x00000000
[ 1234.665038] ffff880129661d38 0000000000000086 ffff880374c7b4d0 ffff880129661fd8
[ 1234.665038] 0000000000004000 0000000000012a40 ffff88017af63180 ffff880179fe3180
[ 1234.665038] ffff880129661c78 ffffffff810ad4f9 0000000000000008 0000000000000002
[ 1234.665038] Call Trace:
[ 1234.665038] [<ffffffff810ad4f9>] ? rcu_is_cpu_idle+0x38/0x57
[ 1234.665038] [<ffffffff81139e51>] ? d_set_d_op+0xb5/0xb5
[ 1234.665038] [<ffffffff813afbcc>] schedule+0x64/0x66
[ 1234.665038] [<ffffffff813afe9a>] schedule_preempt_disabled+0x18/0x24
[ 1234.665038] [<ffffffff813ae900>] __mutex_lock_slowpath+0x156/0x1c2
[ 1234.665038] [<ffffffff813adbad>] mutex_lock+0x18/0x29
[ 1234.665038] [<ffffffff810bfaad>] tracing_reset_all_online_cpus+0x12/0x49
[ 1234.665038] [<ffffffff810cd105>] trace_module_notify+0x27b/0x2a2
[ 1234.665038] [<ffffffff81060aab>] notifier_call_chain+0x37/0x63
[ 1234.665038] [<ffffffff81060be9>] __blocking_notifier_call_chain+0x4b/0x60
[ 1234.665038] [<ffffffff81060c12>] blocking_notifier_call_chain+0x14/0x16
[ 1234.665038] [<ffffffff8108cf62>] SyS_delete_module+0x228/0x274
[ 1234.665038] [<ffffffff813b1d82>] system_call_fastpath+0x16/0x1b
I haven't verified how reproducible this is yet.
--
Gleb.
next reply other threads:[~2013-07-21 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 11:52 Gleb Natapov [this message]
2013-07-21 12:14 ` module unloading hangs after using ftrace with 3.11.0-rc1 Gleb Natapov
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=20130721115215.GG20379@redhat.com \
--to=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.