linux-kernel - Re: [PATCH] FTRACE_STARTUP_TEST should depend on FTRACE.

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

Message-ID: <20080915071732.GA24442@elte.hu>
Date:	Mon, 15 Sep 2008 09:17:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Noonan <steven@...inklabs.net>
Cc:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] FTRACE_STARTUP_TEST should depend on FTRACE.

* Steven Noonan <steven@...inklabs.net> wrote:

> Doesn't make sense to do an FTRACE startup test when FTRACE isn't even 
> being compiled in.

hm, not sure - there is a bit of a dual personality here: 'ftrace' also 
means the 'function tracer', which is one of the tracers implemented in 
kernel/trace/*. The correct dependency is on CONFIG_TRACING - and 
CONFIG_FTRACE_STARTUP_TEST already depends on that.

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