From: Szymon Janc <szymon.janc@tieto.com>
To: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] android/client: Check if hex string is byte format
Date: Fri, 05 Sep 2014 15:28:28 +0200 [thread overview]
Message-ID: <2083072.L6pR49dnTk@uw000953> (raw)
In-Reply-To: <1409921307-31445-2-git-send-email-grzegorz.kolodziejczyk@tieto.com>
Hi Grzegorz,
On Friday 05 of September 2014 14:48:27 Grzegorz Kolodziejczyk wrote:
> Data strings should be byte format.
> ---
> android/client/if-gatt.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/android/client/if-gatt.c b/android/client/if-gatt.c
> index c8352b5..5cae7e8 100644
> --- a/android/client/if-gatt.c
> +++ b/android/client/if-gatt.c
> @@ -803,6 +803,10 @@ static int fill_buffer(const char *str, uint8_t *out, int out_size)
>
> str_len = strlen(str);
>
> + /* Hex string must be byte format */
> + if (str_len%2 != 0)
if (str_len % 2)
> + return -1;
> +
> for (i = 0, j = 0; i < out_size && j < str_len; i++, j++) {
> c = str[j];
>
> @@ -1201,6 +1205,10 @@ static void write_characteristic_p(int argc, const char **argv)
> }
>
> GET_VERIFY_HEX_STRING(argv[6], value, len);
> + if (len < 0) {
> + haltest_error("Value must be byte hex string\n");
> + return;
> + }
Move this check to GET_VERIFY_HEX_STRING() macro (after fill_bufer()) so that
all users gets updated.
>
> /* auth_req */
> if (argc > 7)
>
--
Best regards,
Szymon Janc
next prev parent reply other threads:[~2014-09-05 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 12:48 [PATCH 1/2] androd/client: Extend history line size and depth Grzegorz Kolodziejczyk
2014-09-05 12:48 ` [PATCH 2/2] android/client: Check if hex string is byte format Grzegorz Kolodziejczyk
2014-09-05 13:28 ` Szymon Janc [this message]
2014-09-05 13:29 ` [PATCH 1/2] androd/client: Extend history line size and depth 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=2083072.L6pR49dnTk@uw000953 \
--to=szymon.janc@tieto.com \
--cc=grzegorz.kolodziejczyk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox