linux-kernel - Re: [PATCH v3 2/4] tracing: Make syscall

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]

Message-ID: <20090824113201.GB10215@elte.hu>
Date:	Mon, 24 Aug 2009 13:32:01 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Paul Mundt <lethal@...ux-sh.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Josh Stone <jistone@...hat.com>, linux-kernel@...r.kernel.org,
	Jason Baron <jbaron@...hat.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Martin Bligh <mbligh@...gle.com>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCH v3 2/4] tracing: Make syscall_(un)regfunc arch-specific


* Paul Mundt <lethal@...ux-sh.org> wrote:

> On Mon, Aug 24, 2009 at 01:00:40PM +0200, Ingo Molnar wrote:
>
> > And the thing is, s390 was always a pleasure to deal with. I 
> > cannot say the same about anything SH. SH always was a huge PITA 
> > to deal with (to me at least), mainly because you seem to have a 
> > false sense of entitlement: you think everyone else must be 
> > perfect and must not affect you while you can sit on your own 
> > little island not worrying about the rest of the world - who 
> > develops and tests core kernel facilities for you. It doesnt 
> > work like that.
> 
> If you had bothered to read any of my earlier mail you would 
> realize that this is complete and utter nonsense.

first you say it's nonsense, then you basically back up my points:

> [...] I expect there to be breakage, and I expect that I will be 
> the one fixing it up (even when most of the time that breakage is 
> not even in my own tree). Unsurprisingly, this is largely a result 
> of SH being one of the first architectures testing these new core 
> kernel facilities, which is something you seem intent on just 
> writing off completely. [...]

... the thing is, you didnt Cc: any of the tracing commits in the SH 
tree either to lkml or to the tracing folks who are developing those 
facilities:

  c652d78: sh: Add ftrace syscall tracing support

  From: Matt Fleming <matt@...sole-pimps.org>
  Date: Mon, 6 Jul 2009 20:16:33 +0900
  Subject: [PATCH] sh: Add ftrace syscall tracing support

  [...]

  Signed-off-by: Matt Fleming <matt@...sole-pimps.org>
  Signed-off-by: Paul Mundt <lethal@...ux-sh.org>

That 'could' have been Cc:-ed to Frederic and Steve, perhaps Jason 
and me as well.

You basically treat SH as your own private tree, with little need to 
communicate with anyone outside the SH hackers. Which is fine, as 
long as you are willing to deal with the other side of the coin: 
that others wont be aware of your changes.

Or, at minimum, to not scream loudly when the flip side beats you.

	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/