linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <bgix@codeaurora.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: Add SMP support to user_confirm_reply
Date: Wed, 09 Nov 2011 14:34:15 -0800	[thread overview]
Message-ID: <4EBAFFE7.2030506@codeaurora.org> (raw)
In-Reply-To: <1320877587.15441.352.camel@aeonflux>

Hi Marcel,

On 11/9/2011 2:26 PM, Marcel Holtmann wrote:

>> +	conn = hci_conn_hash_lookup_ba(hdev, ACL_LINK,&cp->bdaddr);
>> +	if (!conn) {
>> +		conn = hci_conn_hash_lookup_ba(hdev, LE_LINK,&cp->bdaddr);
>> +		if (!conn) {
>> +			err = cmd_status(sk, index, mgmt_op, ENOTCONN);
>> +			goto done;
>> +		}
>> +
>> +		/* Forward Confirm response to SMP */
>> +
>> +		err = cmd_status(sk, index, mgmt_op, 0);
>> +		goto done;
>> +
>>   	}
>
> I am a bit lost why we are trying to find an ACL_LINK here first.

We want to route the confirmation to the Secure Simple Pair HCI command 
if this is being done on an ACL link, and to the SMP pairing algorythm 
if it is being done on an LE link.

While I suppose we could route all non-LE results to the related HCI 
command, it seemed cleaner to me to reject it with an ENOTCONN, rather 
than make an invalid HCI call, and depending on the baseband generating 
the error.

-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2011-11-09 22:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 19:13 [PATCH 0/2] Add SMP MITM hooks into MGMTOPS Brian Gix
2011-11-09 19:13 ` [PATCH 1/2] Bluetooth: Add SMP support to user_confirm_reply Brian Gix
2011-11-09 22:26   ` Marcel Holtmann
2011-11-09 22:34     ` Brian Gix [this message]
2011-11-09 22:44       ` Marcel Holtmann
2011-11-09 19:13 ` [PATCH 2/2] Bluetooth: Add Passkey for SSP & SMP pairing Brian Gix
2011-11-09 22:33   ` Marcel Holtmann

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=4EBAFFE7.2030506@codeaurora.org \
    --to=bgix@codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).