From: Brian Gix <bgix@codeaurora.org>
To: linux-bluetooth@vger.kernel.org,
Gustavo Padovan <padovan@profusion.mobi>
Cc: Brian Gix <bgix@codeaurora.org>
Subject: [PATCH-v4 3/9] Bluetooth: Differentiate LE User Pairing Responses
Date: Wed, 16 Nov 2011 13:53:14 -0800 [thread overview]
Message-ID: <1321480400-17397-4-git-send-email-bgix@codeaurora.org> (raw)
In-Reply-To: <1321480400-17397-1-git-send-email-bgix@codeaurora.org>
Low Energy (LE) pairing responses must be recognized and handled
differently from BR/EDR pairing responses. BR/EDR responses are
handled via HCI commands by the LMP layer, and LE responses are
handled by the Host.
Signed-off-by: Brian Gix <bgix@codeaurora.org>
---
net/bluetooth/mgmt.c | 24 ++++++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
index 394222e..c06a05c 100644
--- a/net/bluetooth/mgmt.c
+++ b/net/bluetooth/mgmt.c
@@ -1587,6 +1587,30 @@ static int user_pairing_resp(struct sock *sk, u16 index, bdaddr_t *bdaddr,
goto done;
}
+ /*
+ * Check for an existing ACL link, if present pair via
+ * HCI commands.
+ *
+ * If no ACL link is present, check for an LE link and if
+ * present, pair via the SMP engine.
+ *
+ * If neither ACL nor LE links are present, fail with error.
+ */
+ conn = hci_conn_hash_lookup_ba(hdev, ACL_LINK, bdaddr);
+ if (!conn) {
+ conn = hci_conn_hash_lookup_ba(hdev, LE_LINK, bdaddr);
+ if (!conn) {
+ err = cmd_status(sk, index, mgmt_op,
+ MGMT_STATUS_NOT_CONNECTED);
+ goto done;
+ }
+
+ /* Continue with pairing via SMP */
+
+ err = cmd_status(sk, index, mgmt_op, MGMT_STATUS_SUCCESS);
+ goto done;
+ }
+
cmd = mgmt_pending_add(sk, mgmt_op, hdev, bdaddr, sizeof(*bdaddr));
if (!cmd) {
err = -ENOMEM;
--
1.7.7.2
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-11-16 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 21:53 [PATCH-v4 0/9] Bluetooth: Add MITM protection to LE-SMP Brian Gix
2011-11-16 21:53 ` [PATCH-v4 1/9] Bluetooth: Add MGMT event for Passkey Entry Brian Gix
2011-11-17 0:57 ` Gustavo Padovan
2011-11-16 21:53 ` [PATCH-v4 2/9] Bluetooth: User Pairing Response restructuring Brian Gix
2011-11-21 15:58 ` Gustavo Padovan
2011-11-16 21:53 ` Brian Gix [this message]
2011-11-21 15:58 ` [PATCH-v4 3/9] Bluetooth: Differentiate LE User Pairing Responses Gustavo Padovan
2011-11-16 21:53 ` [PATCH-v4 4/9] Bluetooth: Add User Passkey Response handling Brian Gix
2011-11-21 15:32 ` Gustavo Padovan
2011-11-16 21:53 ` [PATCH-v4 5/9] Bluetooth: Add HCI User Passkey Req Evt handling Brian Gix
2011-11-16 23:47 ` Vinicius Costa Gomes
2011-11-21 15:35 ` Gustavo Padovan
2011-11-16 21:53 ` [PATCH-v4 6/9] Bluetooth: Cleanup blkcipher on SMP termination Brian Gix
2011-11-21 15:48 ` Gustavo Padovan
2011-11-22 17:47 ` Brian Gix
2011-11-16 21:53 ` [PATCH-v4 7/9] Bluetooth: Centralize SMP pairing failure handling Brian Gix
2011-11-16 21:53 ` [PATCH-v4 8/9] Bluetooth: Add MITM mechanism to LE-SMP Brian Gix
2011-11-17 0:15 ` Vinicius Costa Gomes
2011-11-16 21:53 ` [PATCH-v4 9/9] Bluetooth: Add SMP to User Passkey and Confirm Brian Gix
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=1321480400-17397-4-git-send-email-bgix@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).