From: Dave Jones <davej@redhat.com>
To: rostedt@goodmis.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
Date: Wed, 29 Jan 2014 23:16:22 -0500 [thread overview]
Message-ID: <20140130041622.GA23875@redhat.com> (raw)
WARNING: CPU: 3 PID: 796 at kernel/trace/ftrace.c:1655 __ftrace_hash_rec_update.part.38+0x20a/0x240()
CPU: 3 PID: 796 Comm: trinity-main Not tainted 3.13.0+ #100
0000000000000009 000000003628f1c9 ffff8802395dfc48 ffffffffb1737a8a
0000000000000000 ffff8802395dfc80 ffffffffb106d28d 0000000000000000
0000000000000001 ffff880221165000 0000000000000000 ffff8801db17c9d8
Call Trace:
[<ffffffffb1737a8a>] dump_stack+0x4e/0x7a
[<ffffffffb106d28d>] warn_slowpath_common+0x7d/0xa0
[<ffffffffb106d3ba>] warn_slowpath_null+0x1a/0x20
[<ffffffffb112128a>] __ftrace_hash_rec_update.part.38+0x20a/0x240
[<ffffffffb1122fff>] ftrace_shutdown+0x1ff/0x330
[<ffffffffb11234f0>] unregister_ftrace_function+0x20/0x40
[<ffffffffb1141a57>] perf_ftrace_event_register+0x87/0x130
[<ffffffffb11418bc>] perf_trace_destroy+0x2c/0x50
[<ffffffffb114cec9>] tp_perf_event_destroy+0x9/0x10
[<ffffffffb114e4b5>] __free_event+0x25/0xb0
[<ffffffffb114e5b7>] free_event+0x77/0x100
[<ffffffffb114e6a4>] perf_event_release_kernel+0x64/0x90
[<ffffffffb114ecdf>] put_event+0xdf/0x130
[<ffffffffb114ec30>] ? put_event+0x30/0x130
[<ffffffffb114ed40>] perf_release+0x10/0x20
[<ffffffffb11c9c4a>] __fput+0xea/0x2c0
[<ffffffffb11c9e6e>] ____fput+0xe/0x10
[<ffffffffb1090a24>] task_work_run+0xb4/0xe0
[<ffffffffb106e835>] do_exit+0x2e5/0xb40
[<ffffffffb174ac7f>] ? ftrace_call+0x5/0x2f
[<ffffffffb107007c>] do_group_exit+0x4c/0xc0
[<ffffffffb1070104>] SyS_exit_group+0x14/0x20
[<ffffffffb174b1e4>] tracesys+0xdd/0xe2
---[ end trace f3c5dcf3f350edcc ]---
1655 if (FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
1656 return;
This old friend came back. I first reported this back in July, and we aparently never
got to the bottom of it.
Dave
next reply other threads:[~2014-01-30 4:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 4:16 Dave Jones [this message]
2014-01-30 4:50 ` FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0)) Steven Rostedt
2014-01-30 5:32 ` Dave Jones
2014-01-30 13:55 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2013-08-28 3:46 Dave Jones
2013-08-28 13:54 ` Steven Rostedt
2013-08-28 13:58 ` Steven Rostedt
2013-08-28 15:17 ` Steven Rostedt
2013-08-28 18:27 ` Dave Jones
2013-08-28 18:29 ` Dave Jones
2013-08-28 19:27 ` Steven Rostedt
2013-09-30 17:12 ` Dave Jones
2013-10-01 3:56 ` Steven Rostedt
2013-10-01 4:20 ` Dave Jones
2013-10-01 12:28 ` Steven Rostedt
2013-10-02 14:16 ` Dave Jones
2013-10-02 16:43 ` Steven Rostedt
2013-10-02 16:53 ` Dave Jones
2013-08-28 14:31 ` Steven Rostedt
2013-08-28 16:23 ` Dave Jones
2013-08-28 16:50 ` Vince Weaver
2013-08-28 16:57 ` Steven Rostedt
2013-08-28 17:33 ` Dave Jones
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=20140130041622.GA23875@redhat.com \
--to=davej@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.