connection: kick off timeout scan for conn_src, not conn_dst

conn_src is the one we added the reply list to, so this one should be
kicked off.

Note that the first invocation of the timeout scanner will unlikely do
any real work anyway. The reason for calling it here is that it will
implicitly calculate a new deadline, and arm the timer.

diff --git a/connection.c b/connection.c
index 5c47c898b3de767d5856cafe296ae6cae1aae549..1ccc3f4036ce54e33cc23e14efa38e91de5c9294 100644 (file)
--- a/connection.c
+++ b/connection.c
@@ -787,7 +787,7 @@ int kdbus_conn_kmsg_send(struct kdbus_ep *ep,
                atomic_inc(&reply->conn->reply_count);
                mutex_unlock(&conn_src->lock);
 
-               kdbus_conn_timeout_schedule_scan(conn_dst);
+               kdbus_conn_timeout_schedule_scan(conn_src);
        }
 
        if (conn_src) {