linux-kernel - Re: kdbus: to merge or not to merge?

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: <6295881.qFxhe0B0Ak@merkaba>
Date:	Wed, 24 Jun 2015 12:46:21 +0200
From:	Martin Steigerwald <martin@...htvoll.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andy Lutomirski <luto@...capital.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Havoc Pennington <havoc.pennington@...il.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Tom Gundersen <teg@...m.no>, Daniel Mack <daniel@...que.org>
Subject: Re: kdbus: to merge or not to merge?

Am Mittwoch, 24. Juni 2015, 10:05:02 schrieb Ingo Molnar:
>  - Once one (or two) major distros go with kdbus, it becomes a de-facto
> ABI. If the ABI is bad then that distro will hurt from it regardless of
> whether we merge it upstream or not - so technical pressure is there to
> improve it. But if the kernel refuses to merge it, Linux users will get
> hurt disproportionately badly. The kernel not being the first mover with
> a new ABI is absolutely sensible. But once Linux distros have taken the
> initial (non-trivial) plunge, not merging a zero-cost ABI upstream
> becomes more like revenge and obstruction, which is not productive. The
> kernel has very little value without full user-space, after all, so
> within reason the kernel project has to own up to distro ABI mistakes as
> well.

So, in order to merge something that is not accepted upstream yet, is it an 
accepted way to encourage distros to use it nonetheless, to get it upstream 
then anyway as in "as, look, now this and this distro uses it"?

When I read

> Not because I like it so much, but because I think the merge process
> should be  stripped of politics and emotion as much as possible: if an
> initial submission is good and addresses all technical review properly,
> and if the cost to the core kernel is low, then barring alternative,
> fully equivalent and superior patch submissions, rejecting it does more
> harm than good.

I think you didn´t mean it that way, as you state proper technical review as 
a requirement.

Can you clarify?


Still as far as I got it, Andy raised technical concerns which Greg 
outrightly rejected as invalid without any further explaination. That does 
not seem like technical concerns have been properly addressed to me.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
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/