aboutsummaryrefslogtreecommitdiff
path: root/ipc
diff options
context:
space:
mode:
authorDavid Herrmann <dh.herrmann@gmail.com>2015-07-06 11:29:05 +0200
committerDavid Herrmann <dh.herrmann@gmail.com>2015-07-06 18:14:51 +0200
commit5b2ae5600065167040dd6d61466cce345568c68e (patch)
tree14507f827850093db431d2a883b1533f554ef2b5 /ipc
parent5c9d1e5ee20da087dee20f20d5fa312249a163e4 (diff)
kdbus: allow senders to receive own broadcasts
The dbus1 spec does not place a restriction on who can receive broadcasts. As long as the sender has a MATCH-rule on itself, it can as well receive its own broadcasts. As it turns out, user-space currently relies on this feature. So make sure to allow this just like dbus1. If we find some client that does not work with this, we will have to turn it into a HELLO-flag. Until then, just try to adjust the default behavior. Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Diffstat (limited to 'ipc')
-rw-r--r--ipc/kdbus/bus.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/ipc/kdbus/bus.c b/ipc/kdbus/bus.c
index e7e17a7f7edd..a67f825bdeaf 100644
--- a/ipc/kdbus/bus.c
+++ b/ipc/kdbus/bus.c
@@ -263,8 +263,6 @@ void kdbus_bus_broadcast(struct kdbus_bus *bus,
down_read(&bus->conn_rwlock);
hash_for_each(bus->conn_hash, i, conn_dst, hentry) {
- if (conn_dst->id == staging->msg->src_id)
- continue;
if (!kdbus_conn_is_ordinary(conn_dst))
continue;