Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Malovany, Ram" <ramm@ti.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v4] Bluetooth: Fix Device Scan and connection collision
Date: Wed, 18 Jul 2012 13:20:27 +0300	[thread overview]
Message-ID: <20120718102027.GA14515@x220.ger.corp.intel.com> (raw)
In-Reply-To: <2683478DEE33CD4DAF508ABCF391F6A40B4AF312@DNCE05.ent.ti.com>

Hi Ram,

On Wed, Jul 18, 2012, Malovany, Ram wrote:
> > >  	e = hci_inquiry_cache_lookup_resolve(hdev, BDADDR_ANY, NAME_NEEDED);
> > > -	if (hci_resolve_name(hdev, e) == 0) {
> > > +	if (e && hci_resolve_name(hdev, e) == 0) {
> > >  		e->name_state = NAME_PENDING;
> > >  		return true;
> > >  	}
> > 
> > This missing NULL check is the first fix. You might actually consider
> > doing:
> > 
> > 	if (!e)
> > 		return false;
> > 
> 
> I didn't want to change the coding in this specific file , as you can
> see in the function:
> 
> hci_inquiry_complete_evt() , calling it the same way. 
> But I can changed them both if needed. Do you want me to ?

The code in hci_inquiry_complete_evt() is a bit different though. There
you have something else instead of a simple return statement if e is
NULL (set the discovery state and unlock hdev) so changing that part
wouldn't really simplify the code much. In your case the code does
however get a bit simpler since all you need to do is return false.

Johan

  reply	other threads:[~2012-07-18 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  7:36 [PATCH v4] Bluetooth: Fix Device Scan and connection collision ramm
2012-07-18  8:24 ` Johan Hedberg
2012-07-18  8:50   ` Malovany, Ram
2012-07-18 10:20     ` Johan Hedberg [this message]
2012-07-18 10:27       ` Malovany, Ram

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=20120718102027.GA14515@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ramm@ti.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