linux-kernel - [RFC] TRACE_EVENT: mapping "=" and memcpy to macros

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

Date:	Mon, 25 Oct 2010 13:39:43 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To:	David Goulet <david.goulet@...ymtl.ca>
Cc:	Nils Carlson <nils.carlson@...csson.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, ltt-dev@...ts.casi.polymtl.ca
Subject: [RFC] TRACE_EVENT: mapping "=" and memcpy to macros

LTTng needs to override the assignment primitives to deal with cross-page
writes. A first step needed to move LTTng to TRACE_EVENT is to introduce the
following macros:

for ftrace and perf:

#define __assign(dest, src)                  (dest) = (src)
#define __assign_memcpy(dest, src, len)      memcpy(dest, src, len)

which would turn (e.g.)

        TP_fast_assign(
                memcpy(__entry->comm, t->comm, TASK_COMM_LEN);
                __entry->pid    = t->pid;
        ),

into

        TP_fast_assign(
                __assign_memcpy(__entry->comm, t->comm, TASK_COMM_LEN);
                __assign(__entry->pid, t->pid);
        ),

So LTTng (and other tracers) can override these with their own primitives. This
is a basic step required to bring the LTTng tree closer to mainline.

Thoughts ?

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
--
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/