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: <20090824111501.GB18420@linux-sh.org>
Date:	Mon, 24 Aug 2009 20:15:01 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	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

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. 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. I can imagine why s390 is a pleasure to deal
with in a -tip context, when you break their tree, no one complains.

Where I take issue with -next is that this is not an isolated thing, and
over time it has only become more frequent. In the case of -mm, releases
were infrequent, but we did have this thing called quality control,
something that is utterly lacking in -next and which the trees being
sucked in seem unable to adhere to on their own.

Rather than wasting any more time on this, we can continue this at kernel
summit during the -next session. If the consensus is that I'm just being
unconstructive and my workflow is inherently broken, I can live with
that.

> You are not being constructive at all.
> 
Nor have been any of your responses. At least we've found something to
agree on!
--
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/