All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] btusb: HCI_QUICK_NO_SUSPEND_NOTIFIER causes kernel panic
@ 2022-11-19 17:00 Mihir Khatri
  2022-11-19 17:13 ` bluez.test.bot
  0 siblings, 1 reply; 3+ messages in thread
From: Mihir Khatri @ 2022-11-19 17:00 UTC (permalink / raw)
  To: linux-bluetooth@vger.kernel.org, marcel@holtmann.org

It seems that setting the bit HCI_QUICK_NO_SUSPEND_NOTIFIER on some fake CSR 5.0 clones can them to get registered 2 times causing a kernel panic. After not setting the bit HCI_QUICK_NO_SUSPEND_NOTIFIER everything works fine and no kernel panic can be observed.

Signed-off-by: Mihir Khatri <MihirKhatri@proton.me>

---

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index e7914783d29e..1bb8d0f2e8b8 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -2267,7 +2267,6 @@ static int btusb_setup_csr(struct hci_dev *hdev)
                set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY, &hdev->quirks);
                set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks);
                set_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks);
-               set_bit(HCI_QUIRK_NO_SUSPEND_NOTIFIER, &hdev->quirks);
 
                /* Clear the reset quirk since this is not an actual
                 * early Bluetooth 1.1 device from CSR.


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-11-22  0:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-19 17:00 [PATCH] btusb: HCI_QUICK_NO_SUSPEND_NOTIFIER causes kernel panic Mihir Khatri
2022-11-19 17:13 ` bluez.test.bot
2022-11-22  0:34   ` Luiz Augusto von Dentz

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.