linux-kernel - Ftrace test failure on MIPS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <50EF71C9.4010907@caviumnetworks.com>
Date:	Thu, 10 Jan 2013 17:58:33 -0800
From:	David Daney <ddaney@...iumnetworks.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Ralf Baechle <ralf@...ux-mips.org>,
	linux-mips <linux-mips@...ux-mips.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Ftrace test failure on MIPS - Looking for insight..

Hi Steven,

I am trying to track down the cause of:

.
.
.
Brought up 32 CPUs
Testing tracer function: PASSED
Testing dynamic ftrace: .. filter failed count=0 ..FAILED!
------------[ cut here ]------------
WARNING: at kernel/trace/trace.c:878 register_tracer+0x23c/0x300()
Modules linked in:
Call Trace:
[<ffffffff815a0578>] dump_stack+0x14/0x40
[<ffffffff8113e8fc>] warn_slowpath_common+0x84/0xb0
[<ffffffff811bd04c>] register_tracer+0x23c/0x300
[<ffffffff81100538>] do_one_initcall+0x110/0x178
[<ffffffff8159234c>] kernel_init+0x174/0x318
[<ffffffff81119de4>] ret_from_kernel_thread+0x14/0x1c

---[ end trace 204112383c2d190e ]---
.
.
.


This is a MIPS64 kernel build from Linus' tree of today (commit 
254adaa465c40151df11fc1f88f93e6e86eb61d4)

I think the failure is long standing (since 3.4.x at least).

If you have any ideas off the top of your head as to what the cause 
might be, I would love to hear them.

In any event, I will try to track down the root cause and fix it.  But 
if something jumped out at you, that could speed up my search for the cause.


Thanks in advance,
David Daney

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/