From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 3/4] shared/gatt-client: Fix bogus asserts
Date: Mon, 1 Feb 2016 16:13:21 +0200 [thread overview]
Message-ID: <1454336002-4954-3-git-send-email-luiz.dentz@gmail.com> (raw)
In-Reply-To: <1454336002-4954-1-git-send-email-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
The asserts involving notify_count were bogus because it should be
possible to disable a notification even before the remote respond to
the write command.
---
src/shared/gatt-client.c | 15 +++++----------
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/src/shared/gatt-client.c b/src/shared/gatt-client.c
index 5fd0208..91acad5 100644
--- a/src/shared/gatt-client.c
+++ b/src/shared/gatt-client.c
@@ -1116,9 +1116,6 @@ static void complete_notify_request(void *data)
{
struct notify_data *notify_data = data;
- /* Increment the per-characteristic ref count of notify handlers */
- __sync_fetch_and_add(¬ify_data->chrc->notify_count, 1);
-
notify_data->att_id = 0;
notify_data->callback(0, notify_data->user_data);
}
@@ -1174,7 +1171,6 @@ static void enable_ccc_callback(uint8_t opcode, const void *pdu,
struct notify_data *notify_data = user_data;
uint16_t att_ecode;
- assert(!notify_data->chrc->notify_count);
assert(notify_data->chrc->ccc_write_id);
notify_data->chrc->ccc_write_id = 0;
@@ -1264,6 +1260,9 @@ static unsigned int register_notify(struct bt_gatt_client *client,
notify_data->id = client->next_reg_id++;
+ /* Increment the per-characteristic ref count of notify handlers */
+ __sync_fetch_and_add(¬ify_data->chrc->notify_count, 1);
+
/*
* If a write to the CCC descriptor is in progress, then queue this
* request.
@@ -1274,9 +1273,9 @@ static unsigned int register_notify(struct bt_gatt_client *client,
}
/*
- * If the ref count is not zero, then notifications are already enabled.
+ * If the ref count > 1, then notifications are already enabled.
*/
- if (chrc->notify_count > 0 || !chrc->ccc_handle) {
+ if (chrc->notify_count > 1 || !chrc->ccc_handle) {
complete_notify_request(notify_data);
return notify_data->id;
}
@@ -1555,7 +1554,6 @@ static void disable_ccc_callback(uint8_t opcode, const void *pdu,
struct notify_data *notify_data = user_data;
struct notify_data *next_data;
- assert(!notify_data->chrc->notify_count);
assert(notify_data->chrc->ccc_write_id);
notify_data->chrc->ccc_write_id = 0;
@@ -2960,9 +2958,6 @@ bool bt_gatt_client_unregister_notify(struct bt_gatt_client *client,
if (!notify_data)
return false;
- assert(notify_data->chrc->notify_count > 0);
- assert(!notify_data->chrc->ccc_write_id);
-
complete_unregister_notify(notify_data);
return true;
}
--
2.5.0
next prev parent reply other threads:[~2016-02-01 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 14:13 [PATCH BlueZ 1/4] shared/gatt-client: Fix not resetting request id Luiz Augusto von Dentz
2016-02-01 14:13 ` [PATCH BlueZ 2/4] core/gatt-client: Fix not being able to cancel notifications Luiz Augusto von Dentz
2016-02-01 14:13 ` Luiz Augusto von Dentz [this message]
2016-02-01 14:13 ` [PATCH BlueZ 4/4] shared/gatt-client: Fix crash unregistering notification Luiz Augusto von Dentz
2016-02-07 16:01 ` [PATCH BlueZ 1/4] shared/gatt-client: Fix not resetting request id 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=1454336002-4954-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).