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: <20150422130739.GA29286@kroah.com>
Date:	Wed, 22 Apr 2015 15:07:39 +0200
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Austin S Hemmelgarn <ahferroin7@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andy Lutomirski <luto@...capital.net>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	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 Mailing List <linux-kernel@...r.kernel.org>,
	Daniel Mack <daniel@...que.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: Issues with capability bits and meta-data in kdbus

On Wed, Apr 22, 2015 at 07:40:25AM -0400, Austin S Hemmelgarn wrote:
> On 2015-04-21 22:32, Linus Torvalds wrote:
> >On Tue, Apr 21, 2015 at 6:54 PM, Andy Lutomirski <luto@...capital.net> wrote:
> >>
> >>If kdbus were a general purpose IPC tool
> >
> >  .. but it's not ..
> >
> 
> Except, IIRC, that was one of the stated design goals in the original patch
> set.  I'm pretty sure that i remember a rather verbose exposition that
> pretty much could be summarized as "Linux has no general purpose IPC in the
> kernel, this fixes that"

Did I say that somewhere?  Here's what the patchset has always started
with every time I have posted it for review, starting back last year in
October:

	kdbus is a kernel-level IPC implementation that aims for
	resemblance to the the protocol layer with the existing
	userspace D-Bus daemon while enabling some features that
	couldn't be implemented before in userspace.

2+ years ago, I had the dream that maybe we could make kdbus into the
"general purpose IPC layer for the kernel", but in working through all
of the issues, and the requirements of the userspace users and
protocols, it just really didn't work out that way, sorry.

I know some people would like such a "general purpose IPC", but perhaps
because no one has ever done it, maybe it either can't be done, or that
no one really wants such a thing. :)

thanks,

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ