summaryrefslogtreecommitdiff
path: root/ipc
diff options
context:
space:
mode:
authorINSUN PYO <insun.pyo@samsung.com>2016-10-11 15:14:46 +0900
committerSeung-Woo Kim <sw0312.kim@samsung.com>2016-12-14 13:53:38 +0900
commit3788bff0f52398a31308f77fef499b2ab0bcdef9 (patch)
treef6183bb32695590b7b138b03b11e689770551805 /ipc
parent7bdd10d2024e6ee01cd7b7048bb1245c41fbd9e3 (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: INSUN PYO <insun.pyo@samsung.com> Change-Id: I83702b59039062967ec2875e268a17d647902a87
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 9d0679eb59f6..cfe997fb4915 100644
--- a/ipc/kdbus/bus.c
+++ b/ipc/kdbus/bus.c
@@ -271,8 +271,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 == kmsg->msg.src_id)
- continue;
if (!kdbus_conn_is_ordinary(conn_dst))
continue;