linux-kernel - Re: [PATCH 1/5] Revert "kmemtrace: fix printk format warnings"

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:	Tue, 19 Aug 2008 14:47:16 -0400
From:	fche@...hat.com (Frank Ch. Eigler)
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	"Randy.Dunlap" <rdunlap@...otime.net>, penberg@...helsinki.fi,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, mpm@...enic.com,
	tglx@...utronix.de, rostedt@...dmis.org, cl@...ux-foundation.org,
	tzanussi@...il.com
Subject: Re: [PATCH 1/5] Revert "kmemtrace: fix printk format warnings"

Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> writes:

> [...]
> Is this kmemtrace marker meant to be exposed to userspace ?
> I suspect not.
> [...]
> Tracepoints = in-kernel tracing API.
> Markers = Data-formatting tracing API, meant to export the data either
> to user-space in text or binary format.

FWIW, that was certainly not the intent of markers.  It was to try to
satisfy both sorts of uses with relative type-safety and a minimum of
code.  Tracepoints may be nice if one needs somewhat (how much?) more
performance, and is willing to burden someone else with the necessary
extra code (such as tracepoint-to-marker conversion modules) to expose
the same data to "userspace" tools like lttng/systemtap.

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