Bluetooth: Don't force DISCOVERY_STOPPED state in inquiry_cache_flush
authorAndre Guedes <andre.guedes@openbossa.org>
Thu, 1 Mar 2012 21:19:57 +0000 (18:19 -0300)
committerJohan Hedberg <johan.hedberg@intel.com>
Fri, 2 Mar 2012 23:43:02 +0000 (01:43 +0200)
commit74fe619ef96466d562a1a13e7cbab783624ec2f3
treeecd5aab7e52b86eddf8ab2461a8a9a4dab1694f0
parent2b4bf3974249da74f4aef1e9180d4beaf6332515
Bluetooth: Don't force DISCOVERY_STOPPED state in inquiry_cache_flush

We are not supposed to force DISCOVERY_STOPPED in inquiry_cache_flush
because we may break the discovery state machine. For instance, during
interleaved discovery, when we are about to start inquiry, the state
machine forcibly goes to DISCOVERY_STOPPED while it should stay in
DISCOVERY_FINDING state.

This problem results in unexpected behaviors such as sending two
mgmt_discovering events to userspace (when only one event is expected)
and Stop Discovery failures.

Signed-off-by: Andre Guedes <andre.guedes@openbossa.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
net/bluetooth/hci_core.c