Bluetooth: Restrict access for raw-only controllers
authorMarcel Holtmann <marcel@holtmann.org>
Sun, 29 Jun 2014 10:13:05 +0000 (12:13 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 3 Jul 2014 15:42:49 +0000 (17:42 +0200)
commitfee746b0babf128a50ece050ee6e63003ebb5ae1
tree4a3c3b7ca76f43ddda0f85b006c023e298d1c3ed
parent958684263d3efbc721fb2b86f94876893eb638d2
Bluetooth: Restrict access for raw-only controllers

Bluetooth controllers that are marked for raw-only usage can only be
used with user channel access. Any other operation should be rejected.

This simplifies the whole raw-only support since it now depends on
the fact that the controller is marked with HCI_QUIRK_RAW_DEVICE and
runtime raw access is restricted to user channel operation.

The kernel internal processing of HCI commands and events is designed
around the case that either the kernel has full control over the device
or that the device is driven from userspace. This now makes a clear
distinction between these two possible operation modes.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
net/bluetooth/hci_conn.c
net/bluetooth/hci_core.c
net/bluetooth/hci_sock.c
net/bluetooth/mgmt.c
This page took 0.025538 seconds and 5 git commands to generate.