From: Djalal Harouni Date: Tue, 14 Oct 2014 21:44:37 +0000 (+0100) Subject: doc: document the new KDBUS_HELLO_ACCEPT_MEMFD flag X-Git-Tag: upstream/0.20141102.012929utc~93 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=947a2e09bdf88dd103738da9d6ac1f4c66be4977;p=platform%2Fcore%2Fsystem%2Fkdbus-bus.git doc: document the new KDBUS_HELLO_ACCEPT_MEMFD flag Signed-off-by: Djalal Harouni --- diff --git a/kdbus.txt b/kdbus.txt index 3a219be..6e8b090 100644 --- a/kdbus.txt +++ b/kdbus.txt @@ -442,6 +442,11 @@ struct kdbus_cmd_hello { as message payload. If it's not set, any attempt of doing so will result in -ECOMM on the sender's side. + KDBUS_HELLO_ACCEPT_MEMFD + When this flag is set, the connection can be sent memfd file + descriptors as message payload. If it's not set, any attempt of + doing so will result in -ECOMM on the sender's side. + KDBUS_HELLO_ACTIVATOR Make this connection an activator (see below). With this bit set, an item of type KDBUS_ITEM_NAME has to be attached which describes @@ -871,9 +876,10 @@ pool. The message is stored as struct kdbus_msg at this offset, and can be interpreted with the semantics described above. Also, if the connection allowed for file descriptor to be passed -(KDBUS_HELLO_ACCEPT_FD), and if the message contained any, they will be -installed into the receiving process after the KDBUS_CMD_MSG_RECV ioctl -returns. The receiving task is obliged to close all of them appropriately. +(KDBUS_HELLO_ACCEPT_FD or KDBUS_HELLO_ACCEPT_MEMFD), and if the message +contained any, they will be installed into the receiving process after the +KDBUS_CMD_MSG_RECV ioctl returns. The receiving task is obliged to close all +of them appropriately. The caller is obliged to call KDBUS_CMD_FREE with the returned offset when the memory is no longer needed.