From: Pedro Monjo Florit <pmonjo2000@yahoo.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Possible bug in sdp.c
Date: Tue, 14 Feb 2006 12:02:54 +0100 [thread overview]
Message-ID: <43F1B8DE.3060206@yahoo.com> (raw)
Hi,
I have seen what *may* be a possible bug in sdp.c. If there is an error
in a SDP PDU sent by a bluetooth device, it seems that the SDP parsing
code in sdp.c enters an infinite loop filling syslog with the following
message: "Unknown sequence type, aborting".
I have been tracking down the cause and I have found where the problem
might be. The function sdp_extract_seqtype() may return 0 in case of
unrecognized data, but this case does not seem to be handled in the
calls to this function (for example, in sdp_service_search_attr_req() or
in sdp_extract_pdu()).
Could anybody tell me whether am I right or wrong? Has anybody seen a
similar behaviour?
Regards,
Pedro
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-02-14 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 11:02 Pedro Monjo Florit [this message]
2006-02-14 12:17 ` [Bluez-devel] Re: Possible bug in sdp.c Pedro Monjo Florit
2006-02-15 8:03 ` Marcel Holtmann
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=43F1B8DE.3060206@yahoo.com \
--to=pmonjo2000@yahoo.com \
--cc=bluez-devel@lists.sourceforge.net \
/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).