From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bug: infinite loop in extract_seq() when sdp_extract_seqtype() fails
Date: Mon, 19 Jun 2006 20:27:27 +0200 [thread overview]
Message-ID: <1150741647.4277.30.camel@localhost> (raw)
In-Reply-To: <F73F58A0-A537-4ACE-8C56-D5F2D6735F61@wideray.com>
Hi Jason,
> >> It appears that extract_seq() in sdp.c (bluez-libs) can enter an
> >> infinite loop if sdp_extract_seqtype() fails when extract_seq() has
> >> called itself recursively. Here's how:
> >
> > Do you have a patch for it or can you send a small reproducer program?
>
> This may be a false alarm. When I looked closer, I could not explain
> how the program could reach the state I described. The problem is
> that sdp_extract_attr() only calls extract_seq() for aggregate
> types. In fact, exactly those types that sdp_extract_seqtype()
> expects. With that invariant, I don't see how the program could fall
> into the loop I described, not without resorting to exotic explanations.
>
> All I know at this point is that /var/log/messages gets an endless
> flood of
>
> sdp_extract_seqtype: Unknown sequence type, aborting
>
> We don't know yet what triggers this. Of course I will follow up if
> it still turns out to be a problem in bluez.
it is kinda likely that SDP still have endless loops in it. However
please make sure you use the latest bluez-libs from CVS and really run
the latest sdpd and/or sdptool.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-19 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 23:01 [Bluez-devel] Bug: infinite loop in extract_seq() when sdp_extract_seqtype() fails Jason Watts
2006-06-17 10:07 ` Marcel Holtmann
2006-06-19 18:08 ` Jason Watts
2006-06-19 18:27 ` Marcel Holtmann [this message]
2006-06-20 7:37 ` Pedro Monjo Florit
2006-06-20 19:54 ` Jason Watts
2006-07-11 22:46 ` Jason Watts
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=1150741647.4277.30.camel@localhost \
--to=marcel@holtmann.org \
--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