Off-topic: D-Bus in the kernel

Ray Strode halfline at
Mon Sep 20 08:22:04 PDT 2010


On Mon, Sep 20, 2010 at 5:30 AM, Richard Hughes <hughsient at> wrote:
> On 17 September 2010 18:52, Ray Strode <halfline at> wrote:
>> In theory if this was handled on the kernel side it could set the
>> login uid properly on the activated process instead of using the login
>> uid of the bus daemon.
> I'm not sure this makes sense, as packagekitd can be auto-started by
> user 'bob' and then used to install a package, and then user 'sally'
> can use the same daemon instance to remove a package. The daemon only
> quits after 10 seconds of idleness.
Ah right, and that's a very reasonable thing for it to do.

> Requiring system-activated daemon to quit after ever user action would
> demolish performance IMHO.
Clearly that would be suboptimal.  There probably needs to be a way to
tell the kernel some "surrogate uid".  It wouldn't have to be the uid
itself, I guess--it could just be the fd of the client connection.

So, you're right, it seems like this isn't something we can solve
solely by putting the system bus in the kernel, since fundamentally it
requires each system service to somehow define client work boundaries,
and only the system service, not the bus and not the kernel know what
those boundaries are.


More information about the dbus mailing list