From: Marcel Holtmann <marcel@holtmann.org>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 2/2] lib: Fix SDP_TEXT_STR16/SDP_URL_STR16 parsing
Date: Tue, 08 Jan 2013 11:13:04 -0800 [thread overview]
Message-ID: <1357672384.1806.34.camel@aeonflux> (raw)
In-Reply-To: <1357670608-19081-2-git-send-email-anderson.lizardo@openbossa.org>
Hi Anderson,
> sdp_extract_attr() uses the "size" parameter to return the number of
> bytes consumed when parsing SDP Data Elements. This size is used to
> advance a buffer pointer to parse next element.
>
> This size was being incorrectly calculated for
> SDP_TEXT_STR16/SDP_URL_STR16, where the string length was added twice.
>
> A unit test added on the previous commit should now pass with this fix.
> ---
> lib/sdp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/sdp.c b/lib/sdp.c
> index ca474cd..b87f392 100644
> --- a/lib/sdp.c
> +++ b/lib/sdp.c
> @@ -1176,7 +1176,7 @@ static sdp_data_t *extract_str(const void *p, int bufsize, int *len)
> }
> n = bt_get_be16(p);
> p += sizeof(uint16_t);
> - *len += sizeof(uint16_t) + n;
> + *len += sizeof(uint16_t);
I do not get this fix. Isn't this str8 and url8 part wrong?
Regards
Marcel
next prev parent reply other threads:[~2013-01-08 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 18:43 [PATCH BlueZ 1/2] unit: Add initial tests for sdp_extract_attr() Anderson Lizardo
2013-01-08 18:43 ` [PATCH BlueZ 2/2] lib: Fix SDP_TEXT_STR16/SDP_URL_STR16 parsing Anderson Lizardo
2013-01-08 19:13 ` Marcel Holtmann [this message]
2013-01-08 20:27 ` Anderson Lizardo
2013-01-08 22:41 ` Marcel Holtmann
2013-01-08 23:05 ` [PATCH v2 BlueZ] " Anderson Lizardo
2013-01-09 2:25 ` Marcel Holtmann
2013-01-08 19:10 ` [PATCH BlueZ 1/2] unit: Add initial tests for sdp_extract_attr() Marcel Holtmann
2013-01-08 20:45 ` Anderson Lizardo
2013-01-08 22:46 ` Marcel Holtmann
2013-01-09 15:14 ` Anderson Lizardo
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=1357672384.1806.34.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=anderson.lizardo@openbossa.org \
--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