linux-kernel - Re: function_graph selftest fails with !DYNAMIC

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 03 Nov 2011 12:08:27 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Rabin Vincent <rabin@....in>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: function_graph selftest fails with !DYNAMIC

On Wed, 2011-11-02 at 20:32 +0530, Rabin Vincent wrote:
> The function_graph selftest fails when CONFIG_DYNAMIC_FTRACE is not set
> (tested on x86-64) on current kernels:
> 
> [    0.300124] Testing tracer function: PASSED
> [    0.446092] Testing tracer function_graph: .. no entries found ..FAILED!
> 
> Bisecting goes back to this commit:
> 
> 2b499381bc50ede01b3d8eab164ca2fad00655f0 is the first bad commit
> commit 2b499381bc50ede01b3d8eab164ca2fad00655f0

Interesting, I get the same bug at HEAD, but when I checked out this
commit, it works.

Maybe I'll kick off a bisect and see where it lands up.

Thanks,

-- Steve

> Author: Steven Rostedt <srostedt@...hat.com>
> Date:   Tue May 3 22:49:52 2011 -0400
> 
>     ftrace: Have global_ops store the functions that are to be traced
>     
>     This is a step towards each ops structure defining its own set
>     of functions to trace. As the current code with pid's and such
>     are specific to the global_ops, it is restructured to be used
>     with the global ops.
>     
>     Signed-off-by: Steven Rostedt <rostedt@...dmis.org>


--
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/