* [PATCH v2] bluetooth: fix hci_dev registration leak in virtbt_probe
@ 2026-06-28 12:16 WenTao Liang
2026-06-28 13:16 ` [v2] " bluez.test.bot
0 siblings, 1 reply; 2+ messages in thread
From: WenTao Liang @ 2026-06-28 12:16 UTC (permalink / raw)
To: linux-bluetooth
Cc: marcel, luiz.dentz, linux-kernel, stable, WenTao Liang, Greg KH
When virtbt_open_vdev fails after hci_register_dev succeeds, the
open_failed error path calls hci_free_dev, which only releases the
allocation reference. The Bluetooth subsystem still holds a registration
reference and keeps the device on hci_dev_list. Fix by calling
hci_unregister_dev first, then hci_free_dev, matching the pattern in
virtbt_remove.
Suggested-by: Greg KH <gregkh@linuxfoundation.org>
Fixes: dc65b4b0f90a ("Bluetooth: virtio_bt: fix device removal")
Cc: stable@vger.kernel.org
Signed-off-by: WenTao Liang <vulab@iscas.ac.cn>
---
Changes in v2:
- Fix patch format based on reviewer feedback
---
drivers/bluetooth/virtio_bt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/bluetooth/virtio_bt.c b/drivers/bluetooth/virtio_bt.c
index 140ab55c9fc5..bf6827431bb8 100644
--- a/drivers/bluetooth/virtio_bt.c
+++ b/drivers/bluetooth/virtio_bt.c
@@ -397,6 +397,7 @@ static int virtbt_probe(struct virtio_device *vdev)
return 0;
open_failed:
+ hci_unregister_dev(hdev);
hci_free_dev(hdev);
failed:
vdev->config->del_vqs(vdev);
--
2.39.5 (Apple Git-154)
^ permalink raw reply related [flat|nested] 2+ messages in thread
* RE: [v2] bluetooth: fix hci_dev registration leak in virtbt_probe
2026-06-28 12:16 [PATCH v2] bluetooth: fix hci_dev registration leak in virtbt_probe WenTao Liang
@ 2026-06-28 13:16 ` bluez.test.bot
0 siblings, 0 replies; 2+ messages in thread
From: bluez.test.bot @ 2026-06-28 13:16 UTC (permalink / raw)
To: linux-bluetooth, vulab
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1117669
---Test result---
Test Summary:
CheckPatch PASS 1.22 seconds
VerifyFixes PASS 0.29 seconds
VerifySignedoff PASS 0.35 seconds
GitLint PASS 0.65 seconds
SubjectPrefix FAIL 0.28 seconds
BuildKernel PASS 25.65 seconds
CheckAllWarning PASS 28.26 seconds
CheckSparse PASS 27.19 seconds
BuildKernel32 PASS 25.18 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 458.09 seconds
IncrementalBuild PASS 24.98 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/364
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-06-28 13:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-28 12:16 [PATCH v2] bluetooth: fix hci_dev registration leak in virtbt_probe WenTao Liang
2026-06-28 13:16 ` [v2] " bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox