Bluetooth: Introduce a flag to track who really initiates authentication
authorJohan Hedberg <johan.hedberg@intel.com>
Thu, 17 Jul 2014 12:35:39 +0000 (15:35 +0300)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 17 Jul 2014 12:39:40 +0000 (14:39 +0200)
commit977f8fce0279e5f96dc5c5068610d60b9ae94802
treeb2a84081d8c112589b06ac044a78b955b2b8becd
parente7cafc45258c852c5176cd421615846e79a3d307
Bluetooth: Introduce a flag to track who really initiates authentication

Even though our side requests authentication, the original action that
caused it may be remotely triggered, such as an incoming L2CAP or RFCOMM
connect request. To track this information introduce a new hci_conn flag
called HCI_CONN_AUTH_INITIATOR.

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