From: Szymon Janc <szymon.janc@tieto.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 07/11] android/gatt: Fix not handling service change ccc write execute
Date: Tue, 13 Jan 2015 14:48:52 +0100 [thread overview]
Message-ID: <2404014.dfCGdSWY2H@uw000953> (raw)
In-Reply-To: <1420708669-32600-7-git-send-email-jakub.tyszkowski@tieto.com>
Hi Jakub,
On Thursday 08 of January 2015 10:17:45 Jakub Tyszkowski wrote:
> This adds prepare and execute write handling on Service Change CCC
> descriptor.
> ---
> android/gatt.c | 36 ++++++++++++++++++++++++++++++++++--
> 1 file changed, 34 insertions(+), 2 deletions(-)
>
> diff --git a/android/gatt.c b/android/gatt.c
> index b749705..c00eb9e 100644
> --- a/android/gatt.c
> +++ b/android/gatt.c
> @@ -171,6 +171,8 @@ struct gatt_device {
> struct queue *autoconnect_apps;
>
> struct queue *pending_requests;
> + bool wait_svc_change_execute_write;
> + uint16_t svc_change_ccc;
> };
>
> struct app_connection {
> @@ -6599,6 +6601,28 @@ static uint8_t write_execute_request(const uint8_t *cmd, uint16_t cmd_len,
> uint8_t value;
> struct pending_request *data;
>
> + /* handle embeded ccc */
> + if (dev->wait_svc_change_execute_write) {
> + uint8_t flags;
> +
> + dec_exec_write_req(cmd, cmd_len, &flags);
This could fail so we should check it, otherwise we might use garbage flags.
> + dev->wait_svc_change_execute_write = false;
> +
> + if (!!flags)
This !! is not needed here.
> + bt_store_gatt_ccc(&dev->bdaddr, dev->svc_change_ccc);
> +
> + if (!pending_execute_write()) {
> + size_t mtu;
> + uint16_t len = 0;
This initialization is not needed.
> + uint8_t *rsp = g_attrib_get_buffer(dev->attrib, &mtu);
> +
> + len = enc_exec_write_resp(rsp);
> + g_attrib_send(dev->attrib, 0, rsp, len, NULL, NULL,
> + NULL);
> + return 0;
> + }
> + }
> +
> /*
> * Check if there was any write prep before.
> * TODO: Try to find better error code if possible
> @@ -7012,8 +7036,16 @@ static void gatt_srvc_change_write_cb(struct gatt_db_attribute *attrib,
> return;
> }
>
> - /* Set services changed indication value */
> - bt_store_gatt_ccc(bdaddr, get_le16(value));
> + switch (opcode) {
> + case ATT_OP_PREP_WRITE_REQ:
> + dev->wait_svc_change_execute_write = true;
> + dev->svc_change_ccc = get_le16(value);
> + break;
> + default:
> + /* Set services changed indication value */
> + bt_store_gatt_ccc(bdaddr, get_le16(value));
> + break;
> + }
>
> gatt_db_attribute_write_result(attrib, id, 0);
> }
>
--
Best regards,
Szymon Janc
next prev parent reply other threads:[~2015-01-13 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 9:17 [PATCH 01/11] android/tester: Use uint16_t for handles Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 02/11] android/tester: Add macro improving pdu send procedure Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 03/11] android/tester: Support remote sending pdu from fragments Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 04/11] android/tester: Use multiple iovecs instead of one large buffer Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 05/11] android/tester: Add case for GATT embeded attributes writes Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 06/11] android/tester: Add case for GATT prep. and exec. write on ccc descr Jakub Tyszkowski
2015-01-13 13:48 ` Szymon Janc
2015-01-08 9:17 ` [PATCH 07/11] android/gatt: Fix not handling service change ccc write execute Jakub Tyszkowski
2015-01-13 13:48 ` Szymon Janc [this message]
2015-01-08 9:17 ` [PATCH 08/11] android/tester: Add GATT Server test for invalid value length for ccc Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 09/11] android/tester: Add case for error passing in GATT server responses Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 10/11] android/tester: Add GATT case for Svc. change invalid offset write Jakub Tyszkowski
2015-01-08 9:17 ` [PATCH 11/11] android/gatt: Verify offset on srvc change ccc write Jakub Tyszkowski
2015-01-13 13:48 ` Szymon Janc
2015-01-13 13:48 ` [PATCH 01/11] android/tester: Use uint16_t for handles Szymon Janc
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=2404014.dfCGdSWY2H@uw000953 \
--to=szymon.janc@tieto.com \
--cc=jakub.tyszkowski@tieto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.