From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 1/8] gdbus: Fix not maintaining message order for signals
Date: Mon, 19 Aug 2013 17:32:52 +0300 [thread overview]
Message-ID: <1376922779-11802-3-git-send-email-luiz.dentz@gmail.com> (raw)
In-Reply-To: <1376922779-11802-1-git-send-email-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
In some cases the order of the messages is altered when a message is
sent without processing the pending signals first, currently this affect
client_check_order unit test:
/gdbus/client_check_order: **
ERROR:unit/test-gdbus-client.c:795:property_check_order: assertion failed: (g_strcmp0(string, "value1") == 0)
As can be observed the value of the property is not yet updated because the
signal it is still pending, once this fix is applied the test pass:
/gdbus/client_check_order: OK
Note that the flushing only works when g_dbus_send_message is used so
places where dbus_connection_send and other variants are called directly
may still change the order.
---
gdbus/object.c | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/gdbus/object.c b/gdbus/object.c
index 2f8ef45..b2ca1c2 100644
--- a/gdbus/object.c
+++ b/gdbus/object.c
@@ -1494,6 +1494,35 @@ DBusMessage *g_dbus_create_reply(DBusMessage *message, int type, ...)
return reply;
}
+static void g_dbus_flush_object(struct generic_data *data)
+{
+ GSList *l;
+
+ if (data->process_id > 0) {
+ g_source_remove(data->process_id);
+ data->process_id = 0;
+ }
+
+ process_changes(data);
+
+ for (l = data->objects; l; l = l->next)
+ g_dbus_flush_object(l->data);
+}
+
+static void g_dbus_flush(DBusConnection *connection)
+{
+ static gboolean flushing = FALSE;
+
+ if (flushing || root == NULL || root->conn != connection)
+ return;
+
+ flushing = TRUE;
+
+ g_dbus_flush_object(root);
+
+ flushing = FALSE;
+}
+
gboolean g_dbus_send_message(DBusConnection *connection, DBusMessage *message)
{
dbus_bool_t result = FALSE;
@@ -1510,6 +1539,9 @@ gboolean g_dbus_send_message(DBusConnection *connection, DBusMessage *message)
goto out;
}
+ /* Flush pending signal to guarantee message order */
+ g_dbus_flush(connection);
+
result = dbus_connection_send(connection, message, NULL);
out:
--
1.8.3.1
next prev parent reply other threads:[~2013-08-19 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 14:32 [PATCH BlueZ 0/8] Fix message order Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ] build: Fix not checking readline.h for bluetooth-player Luiz Augusto von Dentz
2013-08-20 12:28 ` Luiz Augusto von Dentz
2013-08-19 14:32 ` Luiz Augusto von Dentz [this message]
2013-08-19 23:59 ` [PATCH BlueZ 1/8] gdbus: Fix not maintaining message order for signals Lucas De Marchi
2013-08-19 14:32 ` [PATCH BlueZ 2/8] gdbus: Add g_dbus_send_message_with_reply Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 3/8] gdbus: Avoid calling dbus_connection_send* Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 4/8] gdbus: Fix emitting PropertiesChanged twice Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 5/8] core: Make use of g_dbus_send_message_with_reply Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 6/8] neard: " Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 7/8] audio/media: " Luiz Augusto von Dentz
2013-08-19 14:32 ` [PATCH BlueZ 8/8] obexd: Make use of g_dbus_send_message* Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1376922779-11802-3-git-send-email-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).