linux-kernel - Re: [patch] introduce TRACE_EVENT_ABI (was Re: TRACE_EVENT

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

Message-ID: <20090923124340.GA6093@infradead.org>
Date:	Wed, 23 Sep 2009 08:43:40 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>, mingo@...e.hu
Subject: Re: [patch] introduce TRACE_EVENT_ABI (was Re: TRACE_EVENT_ABI ?)

I'm not sure we can support any as an ABI yet.  The text format seems to
volatile in general - not just the output of the individual trace events
but also the common file format, and for the binary format we need to
figure a good way to tag the output yet.   Also when we define one as
one ABI we should make very clear what that means, e.g. does it have to stay
exactly as is?  Or can we add new fields but not remove old one?

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