diff options
author | Marcel Holtmann <marcel@holtmann.org> | 2015-06-06 06:06:49 +0200 |
---|---|---|
committer | Johan Hedberg <johan.hedberg@intel.com> | 2015-06-08 11:04:49 +0300 |
commit | 781f899f2f9d8b71e35225a087f90052059486c5 (patch) | |
tree | 6cdbb0c74bedbb30f0e8abf68e94f943b51b977b /net/rds | |
parent | 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 (diff) | |
download | talos-obmc-linux-781f899f2f9d8b71e35225a087f90052059486c5.tar.gz talos-obmc-linux-781f899f2f9d8b71e35225a087f90052059486c5.zip |
Bluetooth: Fix race condition with user channel and setup stage
During the initial setup stage of a controller, the low-level transport
is actually active. This means that HCI_UP is true. To avoid toggling
the transport off and back on again for normal operation the kernel
holds a grace period with HCI_AUTO_OFF that will turn the low-level
transport off in case no user is present.
The idea of the grace period is important to avoid having to initialize
all of the controller twice. So legacy ioctl and the new management
interface knows how to clear this grace period and then start normal
operation.
For the user channel operation this grace period has not been taken into
account which results in the problem that HCI_UP and HCI_AUTO_OFF are
set and the kernel will return EBUSY. However from a system point of
view the controller is ready to be grabbed by either the ioctl, the
management interface or the user channel.
This patch brings the user channel to the same level as the other two
entries for operating a controller.
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'net/rds')
0 files changed, 0 insertions, 0 deletions