linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Mike <puffy.taco@gmail.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: reverse SDP issue
Date: Tue, 20 Mar 2012 14:35:46 -0300	[thread overview]
Message-ID: <20120320173546.GA6307@samus> (raw)
In-Reply-To: <20120319230436.GA27304@x220>

Hi,

On 20:04 Mon 19 Mar, Johan Hedberg wrote:
> Hi Mike,
> 
> On Mon, Mar 19, 2012, Mike wrote:
> > I notice a change in commit d2920be715974795b51f9cc3279947104da3647b
> > [1] that changes the "reverse" variable for an SDP query:
> > 
> >  -       device_browse_sdp(device, NULL, NULL, NULL, TRUE);
> > +       if (device_is_bredr(device))
> > +               device_browse_sdp(device, NULL, NULL, NULL, FALSE);
> > +       else
> > +               device_browse_primary(device, NULL, NULL, FALSE);
> > 
> > You can see the original had reverse as TRUE, but the patch may have
> > inadvertently changed it to FALSE..kernel.org/majordomo-info.html
> 
> That looks like a definitive bug. Good that you caught it. Vinicius
> (author of the commit) care to comment?

It was changed to false by mistake, a patch to fix it should be arriving
on the mailing list in a few moments.

The comment on src/device.c around line 1683 gives some hints on what
my mistake may have caused: it could be that the device while connected
"hides" some items from its service record. So with reverse set to
false, some records that are present are being removed by mistake.

> 
> As for the partial service removal changes to the device driver API, it
> looks pretty messy to me. Is there any reason why we couldn't just
> restrict calling remove() for when removing the entire device object
> (and never call it when doing subsequent service discoveries)?

I agree that the logic is quite messy. Just some comments:

That assumes that the service list that a device implements is very much
static, which only breaks for development (in which the services of an 
device are always changing) and you will need to remove that device and 
create it again.

> 
> Johan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Cheers,
-- 
Vinicius

  reply	other threads:[~2012-03-20 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 22:19 reverse SDP issue Mike
2012-03-19 22:36 ` Mike
2012-03-19 23:04 ` Johan Hedberg
2012-03-20 17:35   ` Vinicius Costa Gomes [this message]
2012-03-20 18:27     ` Mike
2012-03-20 18:39       ` Mike
2012-03-20 19:21         ` Mike
2012-03-20 20:18           ` Mike
2012-03-21 12:45     ` Johan Hedberg
2012-03-21 13:11       ` Query on attribute api service object path Jaganath
2012-03-21 14:18         ` Anderson Lizardo
2012-03-21 14:27           ` Jaganath

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=20120320173546.GA6307@samus \
    --to=vinicius.gomes@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=puffy.taco@gmail.com \
    /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).