Bluetooth: Fix setting conn->pending_sec_level value from link key
authorJohan Hedberg <johan.hedberg@intel.com>
Wed, 19 Nov 2014 12:53:04 +0000 (14:53 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Wed, 19 Nov 2014 15:17:32 +0000 (16:17 +0100)
commitcb6f3f7ace0e61285db22508a9efd8a5aeca0af5
treec364e1fa331b3ace2697fadb1b7a7ff9aca4ea5a
parent22a3ceabf152c7c88afa9e34ea33fc3fa55e6cf8
Bluetooth: Fix setting conn->pending_sec_level value from link key

When a connection is requested the conn->pending_sec_level value gets
set to whatever level the user requested the connection to be. During
the pairing process there are various sanity checks to try to ensure
that the right length PIN or right IO Capability is used to satisfy the
target security level. However, when we finally get hold of the link key
that is to be used we should still set the actual final security level
from the key type.

This way when we eventually get an Encrypt Change event the correct
value gets copied to conn->sec_level.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/hci_event.c