Hi Johan, > We need to let the setup stage complete cleanly even when the HCI device > is rfkilled. Otherwise the HCI device will stay in an undefined state > and never get notified to user space through mgmt (even when it gets > unblocked through rfkill). > > This patch makes sure that hci_dev_open() can be called in the HCI_SETUP > stage, that blocking the device doesn't abort the setup stage, and that > the device gets proper powered down as soon as the setup stage completes > in case it was blocked meanwhile. > > The bug that this patch fixed can be very easily reproduced using e.g. > the rfkill command line too. By running "rfkill block all" before > inserting a Bluetooth dongle the resulting HCI device goes into a state > where it is never announced over mgmt, not even when "rfkill unblock all" > is run. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > Cc: stable@xxxxxxxxxxxxxxx > --- > v3: Use "else if" instead of separate if-statement > > net/bluetooth/hci_core.c | 15 ++++++++++++--- > 1 file changed, 12 insertions(+), 3 deletions(-) Acked-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
