linux-kernel - Re: [RFC][PATCH 00/19] tracing: Remove "ftrace" from TRACE

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:	Fri, 22 May 2015 14:28:57 +0200
From:	Daniel Wagner <wagi@...om.org>
To:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org
CC:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Jiri Olsa <jolsa@...nel.org>
Subject: Re: [RFC][PATCH 00/19] tracing: Remove "ftrace" from TRACE_EVENT
 files

Hi Steven,

On 05/14/2015 05:13 PM, Steven Rostedt wrote:
> Although the name "ftrace" is used to describe the kernel tracing
> infrastructure, in actuality it is really just the function hook
> infrastructure. The TRACE_EVENT system is more generic and is used
> by tracing, perf and lttng as well as others.
> 
> This gets confusing at times, as it is not consistent in the naming.
> The kernel should only use "ftrace" when describing the function hook
> infrastructure. For trace_events and recording, it really should just
> use "trace".
> 
> This only changes the internal infrastructure code and to make sure
> such a large change has no impact, I tested it by merging this branch
> into linux-next and building an allmodconfig. There were no build
> failures or warnings due to this change set.
> 
> I plan on doing further testing and hopefully get this ready for 4.2.
> When my testing is complete, I'll be pushing this into linux-next.

I compiled each patch individually and did some smoke testing. No
problems found so far. I don't know if that already classifies for the
Tested-by tag, though feel free adding it.

cheers,
daniel
--
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/