linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Yariv <ido@wizery.com>
To: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Arik Nemtsov <arik@wizery.com>
Subject: Re: [RFC] Bluetooth: Search global l2cap channels by src/dst addresses
Date: Wed, 7 Mar 2012 18:17:14 +0200	[thread overview]
Message-ID: <20120307161714.GA6802@WorkStation> (raw)
In-Reply-To: <20120307103520.GF3647@aemeltch-MOBL1>

Hi Andrei,

On Wed, Mar 07, 2012 at 12:35:22PM +0200, Andrei Emeltchenko wrote:
> Hi Ido,
> 
> On Mon, Mar 05, 2012 at 08:10:24PM +0200, Ido Yariv wrote:
> > The cid or psm and the source address might not be enough to uniquely
> > identify a global channel, especially when the source address is our
> > own.
> > 
> > For instance, when trying to communicate with two LE devices in master
> > mode, data received from the both devices is sent to the same socket.
> > 
> > Fix this by taking the destination address into account when choosing
> > the socket.
> > 
> > Signed-off-by: Ido Yariv <ido@wizery.com>
> > Signed-off-by: Arik Nemtsov <arik@wizery.com>
> > ---

...

> > @@ -847,14 +849,24 @@ static struct l2cap_chan *l2cap_global_chan_by_scid(int state, __le16 cid, bdadd
> >  			continue;
> >  
> >  		if (c->scid == cid) {
> > +			int src_match, dst_match;
> > +			int src_any, dst_any;
> > +
> > +			src_match = !bacmp(&bt_sk(sk)->src, src);
> > +			dst_match = !bacmp(&bt_sk(sk)->dst, dst);
> > +			src_any = !bacmp(&bt_sk(sk)->src, BDADDR_ANY);
> > +			dst_any = !bacmp(&bt_sk(sk)->dst, BDADDR_ANY);
> 
> This may be not efficient to use extensive memcmp operations every time
> before they can be actually used.
> 
> > +
> >  			/* Exact match. */
> > -			if (!bacmp(&bt_sk(sk)->src, src)) {
> > +			if (src_match && dst_match) {
> >  				read_unlock(&chan_list_lock);
> >  				return c;
> >  			}
> 
> at least src_any and dst_any may be put here. Maybe you could improve it
> even more.

Sure, I'll send an updated version.

Thanks for the review,
Ido.

  reply	other threads:[~2012-03-07 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 18:10 [RFC] Bluetooth: Search global l2cap channels by src/dst addresses Ido Yariv
2012-03-07 10:35 ` Andrei Emeltchenko
2012-03-07 16:17   ` Ido Yariv [this message]
2012-03-07 19:04   ` [RFC v2] " Ido Yariv

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=20120307161714.GA6802@WorkStation \
    --to=ido@wizery.com \
    --cc=andrei.emeltchenko.news@gmail.com \
    --cc=arik@wizery.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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).