From: "Jörn Engel" <joern@logfs.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, steve@purestorage.com
Subject: Re: __ftrace_hash_rec_update FTRACE_WARN_ON.
Date: Wed, 24 Jul 2013 12:04:22 -0400 [thread overview]
Message-ID: <20130724160422.GA3641@logfs.org> (raw)
In-Reply-To: <1373036034.22688.155.camel@gandalf.local.home>
On Fri, 5 July 2013 10:53:54 -0400, Steven Rostedt wrote:
>
> Can you find an easy reproducer for this?
We might have found something:
Jul 23 19:00:59 [28253.487058,08] WARNING: at kernel/trace/ftrace.c:1529 __ftrace_hash_rec_update+0x1e3/0x230()
Jul 23 19:00:59 [28253.487203,08] Pid: 20903, comm: bash Tainted: G O 3.6.11+ #38405.trunk
Jul 23 19:00:59 [28253.487206,08] Call Trace:
Jul 23 19:00:59 [28253.487213,08] [<ffffffff8103e5ff>] warn_slowpath_common+0x7f/0xc0
Jul 23 19:00:59 [28253.487218,08] [<ffffffff8103e65a>] warn_slowpath_null+0x1a/0x20
Jul 23 19:00:59 [28253.487222,08] [<ffffffff810c2ee3>] __ftrace_hash_rec_update+0x1e3/0x230
Jul 23 19:00:59 [28253.487227,08] [<ffffffff810c4f28>] ftrace_hash_move+0x28/0x1d0
Jul 23 19:00:59 [28253.487232,08] [<ffffffff811401cc>] ? kfree+0x2c/0x110
Jul 23 19:00:59 [28253.487237,08] [<ffffffff810c68ee>] ftrace_regex_release+0x8e/0x150
Jul 23 19:00:59 [28253.487242,08] [<ffffffff81149f1e>] __fput+0xae/0x220
Jul 23 19:00:59 [28253.487247,08] [<ffffffff8114a09e>] ____fput+0xe/0x10
Jul 23 19:00:59 [28253.487252,08] [<ffffffff8105fa22>] task_work_run+0x72/0x90
Jul 23 19:00:59 [28253.487257,08] [<ffffffff810028ec>] do_notify_resume+0x6c/0xc0
Jul 23 19:00:59 [28253.487262,08] [<ffffffff8126596e>] ? trace_hardirqs_on_thunk+0x3a/0x3c
Jul 23 19:00:59 [28253.487267,08] [<ffffffff815c0f88>] int_signal+0x12/0x17
Jul 23 19:00:59 [28253.487271,08] ---[ end trace 793179526ee09b2c ]---
Jul 23 19:21:02 [ 775.393547,08] WARNING: at kernel/trace/ftrace.c:1529 __ftrace_hash_rec_update+0x1e3/0x230()
Jul 23 19:21:02 [ 775.393715,08] Pid: 6376, comm: bash Tainted: G O 3.6.11+ #38405.trunk
Jul 23 19:21:02 [ 775.393718,08] Call Trace:
Jul 23 19:21:02 [ 775.393727,08] [<ffffffff8103e5ff>] warn_slowpath_common+0x7f/0xc0
Jul 23 19:21:02 [ 775.393732,08] [<ffffffff8103e65a>] warn_slowpath_null+0x1a/0x20
Jul 23 19:21:02 [ 775.393737,08] [<ffffffff810c2ee3>] __ftrace_hash_rec_update+0x1e3/0x230
Jul 23 19:21:02 [ 775.393741,08] [<ffffffff810c4f28>] ftrace_hash_move+0x28/0x1d0
Jul 23 19:21:02 [ 775.393748,08] [<ffffffff811401cc>] ? kfree+0x2c/0x110
Jul 23 19:21:02 [ 775.393754,08] [<ffffffff810c68ee>] ftrace_regex_release+0x8e/0x150
Jul 23 19:21:02 [ 775.393771,08] [<ffffffff81149f1e>] __fput+0xae/0x220
Jul 23 19:21:02 [ 775.393784,08] [<ffffffff8114a09e>] ____fput+0xe/0x10
Jul 23 19:21:02 [ 775.393792,08] [<ffffffff8105fa22>] task_work_run+0x72/0x90
Jul 23 19:21:02 [ 775.393798,08] [<ffffffff810028ec>] do_notify_resume+0x6c/0xc0
Jul 23 19:21:02 [ 775.393804,08] [<ffffffff8126596e>] ? trace_hardirqs_on_thunk+0x3a/0x3c
Jul 23 19:21:02 [ 775.393810,08] [<ffffffff815c0f88>] int_signal+0x12/0x17
Jul 23 19:21:02 [ 775.393814,08] ---[ end trace 3b86cc549cc5483e ]---
If I understand Steve correctly, you have to enable a trace somewhere
in a module, them rmmod that module without disabling the trace. Easy
enough to avoid, but maybe you are interested.
Jörn
--
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision.
-- Bertrand Russell
next prev parent reply other threads:[~2013-07-24 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 14:26 __ftrace_hash_rec_update FTRACE_WARN_ON Dave Jones
2013-07-05 14:53 ` Steven Rostedt
2013-07-05 15:11 ` Dave Jones
2013-07-24 16:04 ` Jörn Engel [this message]
2013-07-25 1:24 ` Steven Rostedt
2013-07-25 5:46 ` Steve Hodgson
2013-07-25 18:59 ` Steven Rostedt
2013-07-26 3:23 ` Steven Rostedt
2013-07-27 19:16 ` Steve Hodgson
2013-07-31 0:51 ` Steven Rostedt
2013-08-02 4:51 ` Steve Hodgson
2013-08-02 11:02 ` 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=20130724160422.GA3641@logfs.org \
--to=joern@logfs.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=steve@purestorage.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