linux-kernel - Re: tracepoint maintainance models

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:	Mon, 18 Sep 2006 01:41:53 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Paul Mundt <lethal@...ux-sh.org>,
	Karim Yaghmour <karim@...rsys.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>, Jes Sorensen <jes@....com>,
	Andrew Morton <akpm@...l.org>,
	Tom Zanussi <zanussi@...ibm.com>,
	Richard J Moore <richardj_moore@...ibm.com>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Michel Dagenais <michel.dagenais@...ymtl.ca>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Christoph Hellwig <hch@...radead.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	William Cohen <wcohen@...hat.com>,
	"Martin J. Bligh" <mbligh@...igh.org>
Subject: Re: tracepoint maintainance models

* Roman Zippel <zippel@...ux-m68k.org> wrote:

> And yet again, you offer no prove at all and just work from 
> assumptions. You throw in some magic "_full set_" of marker and just 
> assume any change in that will completely break static tracers. [...]

i'm not sure i understand what you are trying to say here. Are you 
saying that if i replaced half of the static markups with function 
attributes (which would still provide equivalent functionality for 
dynamic tracers), or if i removed a few dozen static markups with 
dynamic scripts (which change too would be transparent to users of 
dynamic tracers), that in this case static tracers would /not/ break? 
[if yes then that would be the most puzzling suggestion ever posed in 
this thread]

> You completely ignore that it might be possible to create some rules 
> and educate users that the amount of exported events can't be 
> completely static.

no serious trace user would accept it if for example half of their 
static tracepoints would go away, because for example they were made 
dynamic (or they were made function attributes).

that's the plain meaning of what i said. Were we to accept static 
tracers, we'd be stuck with the full set of static tracepoints for a 
long time, because users of static tracers would not accept a 
significant reduction in the number of tracepoints. (even if those 
"reduced" tracepoints were in fact just moved over to dynamic probes)

Was it truly confusing to you what i said? (in words that i thought were 
more than clear) Please let me know and i'll try to formulate more 
verbosely and more clearly when replying to you. This must be some 
fundamental communication issue between you and me.

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