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]

Date:	Wed, 15 Apr 2015 10:48:12 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Richard Weinberger <richard.weinberger@...il.com>
Cc:	Andy Lutomirski <luto@...capital.net>,
	Al Viro <viro@...iv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
	"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 Wed, Apr 15, 2015 at 08:54:07AM +0200, Richard Weinberger wrote:
> On Wed, Apr 15, 2015 at 3:36 AM, Andy Lutomirski <luto@...capital.net> wrote:
> >> We had been there before.  To paraphrase another... meticulously honorable
> >> person, "if you didn't want something relied upon, why have you put it into the
> >> kernel?" Said person is on the record as having no problem whatsoever with
> >> adding dependencies to the bottom of userland stack.
> >
> > It appears that, if kdbus is merged, upstream udev may end up requiring it:
> >
> > http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html
> 
> Why so surprised?
> kdbus will be a major hard-dependency for every non-trivial userland.
> Like cgroups...

Maybe because things like cgroups, and kdbus in the future, solves a
need that the developers in that area have to solve problems and
provide functionality that their users require?

Look, us kernel developers only work on one huge, multithreaded, global
state binary.  Our experience in multi-application interactions with
shared state and permission requirements is usually quite limited.  If
you don't trust the developers of those programs outside the kernel,
don't use them, there are still distros out there that don't require
them.

But if you do trust them, then don't make snide comments about how they
don't know what they are doing, because that's just flat out rude.

greg k-h
--
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/