linux-kernel - Re: [PATCH 3/3] tracing: introduce a trace_data

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]

Date:	Mon, 3 Mar 2014 15:59:42 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Filipe Brandenburger <filbranden@...gle.com>,
	Li Zefan <lizefan@...wei.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] tracing: introduce a trace_data_offset struct to
 store array size

On Mon, 3 Mar 2014 15:48:26 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> without patch:
> 
>          pst2pdf-3506  [000]   120.700910: sched_process_exec: filename=/usr/bin/pst2pdf pid=3506 old_pid=3506
> 
> 
> With patch:
> 
>          pstopnm-4432  [001]  1490.246765: sched_process_exec: filename= pid=4432 old_pid=4432

Now, after applying the following patch to your patch, I was able to
get this again:

         pst2pdf-3512  [000]    99.693582: sched_process_exec: filename=/usr/bin/pst2pdf pid=3512 old_pid=3512


-- Steve

diff --git a/include/linux/ftrace_event.h b/include/linux/ftrace_event.h
index 67e4122..2c6d1b0 100644
--- a/include/linux/ftrace_event.h
+++ b/include/linux/ftrace_event.h
@@ -124,8 +124,13 @@ struct trace_event {
 };
 
 struct trace_array_offset {
+#ifdef __BIG_ENDIAN
+	u16			length;
+	u16			offset;
+#else
 	u16			offset;
 	u16			length;
+#endif
 };
 
 extern int register_ftrace_event(struct trace_event *event);
--
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/