linux-kernel - Re: [GIT PULL] kdbus for 4.1-rc1

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: <alpine.LNX.2.00.1504150024570.26287@pobox.suse.cz>
Date:	Wed, 15 Apr 2015 00:33:30 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:	Andy Lutomirski <luto@...capital.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Tom Gundersen <teg@...m.no>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daniel Mack <daniel@...que.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

On Tue, 14 Apr 2015, Greg Kroah-Hartman wrote:

> Yes, it's an unfortunate design, but one that we are all stuck with 
> (think of it as having to implement code for horrid hardware that you 
> have to get to work properly.)  

Greg, I personally consider this a rather defunct analogy. Broken hardware 
comes from "outter space" we just have to live with somehow, and 
eventually try to gradually improve by working with vendors (and you 
yourself have of course made huge improvements in this very area).

Linux userspace is coming, well, from Linux developers. The sole fact that 
someone wrote a daemon that runs on Linux seems like a very poor 
justification for sucking the daemon into kernel "because we have to live 
with it". 
Userspace has to live with it somehow (and eventually fix itself if 
necessary), yes. Why should kernel just contribute to this "unfortunate 
design" if it really isn't, in any way, obliged or forced to do so?

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
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/