linux-kernel - Re: kdbus: add code for buses, domains and endpoints

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: <546EF464.5060109@gmail.com>
Date:	Fri, 21 Nov 2014 09:14:28 +0100
From:	Harald Hoyer <harald.hoyer@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, arnd@...db.de,
	ebiederm@...ssion.com, gnomes@...rguk.ukuu.org.uk, teg@...m.no,
	jkosina@...e.cz, luto@...capital.net, linux-api@...r.kernel.org,
	linux-kernel@...r.kernel.org
CC:	daniel@...que.org, dh.herrmann@...il.com, tixxdz@...ndz.org
Subject: Re: kdbus: add code for buses, domains and endpoints

On 21.11.2014 06:02, Greg Kroah-Hartman wrote:
> From: Daniel Mack <daniel@...que.org>
> 
> Add the logic to handle the following entities:
> 
> Domain:
>   A domain is an unamed object containing a number of buses. A
>   domain is automatically created when an instance of kdbusfs
>   is mounted, and destroyed when it is unmounted.
>   Every domain offers its own "control" device node to create
>   buses.  Domains have no connection to each other and cannot
>   see nor talk to each other.
> 
> Bus:
>   A bus is a named object inside a domain. Clients exchange messages
>   over a bus. Multiple buses themselves have no connection to each
>   other; messages can only be exchanged on the same bus. The default
>   entry point to a bus, where clients establish the connection to, is
>   the "bus" device node /dev/kdbus/<bus name>/bus.  Common operating
>   system setups create one "system bus" per system, and one "user
>   bus" for every logged-in user. Applications or services may create
>   their own private named buses.

might need a resync with the documentation.

Bus:
  A bus is a named object inside a domain. Clients exchange messages
  over a bus. Multiple buses themselves have no connection to each other;
  messages can only be exchanged on the same bus. The default entry point to
  a bus, where clients establish the connection to, is the "bus" file
  /sys/fs/kdbus/<bus name>/bus.
  Common operating system setups create one "system bus" per system, and one
  "user bus" for every logged-in user. Applications or services may create
   their own private named buses. See section 5 for more details.


--
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/