aboutsummaryrefslogtreecommitdiffstats
path: root/net/bluetooth/hci_conn.c
diff options
context:
space:
mode:
authorJohan Hedberg <johan.hedberg@intel.com>2014-03-19 11:00:49 -0400
committerMarcel Holtmann <marcel@holtmann.org>2014-03-19 16:56:30 -0400
commit4e7b2030c452e5d885d36d4f44ef33d6ceb9759a (patch)
tree6ef6b9ecd8dfeb8a9d6532f0a466712219b444b1 /net/bluetooth/hci_conn.c
parent01ad34d267475ac3387d7ab803a2225b392dae91 (diff)
Bluetooth: Fix Pair Device response parameters for pairing failure
It is possible that pairing fails after we've already received remote identity information. One example of such a situation is when re-encryption using the LTK fails. In this case the hci_conn object has already been updated with the identity address but user space does not yet know about it (since we didn't notify it of the new IRK yet). To ensure user space doesn't get a Pair Device command response with an unknown address always use the same address in the response as was used for the original command. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/hci_conn.c')
0 files changed, 0 insertions, 0 deletions