All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [Patch] Samsung D600 (sdp, service discovery deadlocks)
Date: Thu, 24 Nov 2005 05:22:08 +0100	[thread overview]
Message-ID: <1132806128.5982.18.camel@blade> (raw)
In-Reply-To: <1132691970.9887.14.camel@localhost.localdomain>

Hi Victor,

> We experienced some deadlock in the bluez library for Samsund-D600 phone
> during service discovery. This is due to incorrect SDP record set
> returned on service inquiry request. The response from the SDP server
> contains service records + some rubbish at the end. So when it tries to
> parse it, sdp_extract_pdu() returns 0 recsize and locks the while()
> loop.

the patch is in the CVS now. Thanks.

> Samsung is informed, but I do not know if they will come up with
> something (have no idea who provides the stack for them, they have a
> Broadcom chip in there)

Don't expect anything.

> P.S. I do not have the phone with me now, otherwise I would send in
> hcidump output. It reports errors when trying to parse at the end of
> response.

I like to have these phones at home for further testing, but getting all
the bad phones is quite an expensive hobby. The donations are not enough
to buy them.

Regards

Marcel




-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-11-24  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 20:39 [Bluez-devel] [Patch] Samsung D600 (sdp, service discovery deadlocks) Victor Shchebatyuk
2005-11-24  4:22 ` Marcel Holtmann [this message]

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=1132806128.5982.18.camel@blade \
    --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 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.