From: Pavel Machek <pavel@ucw.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
hidave.darkstar@gmail.com, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: [patch] document hci_usb as broken
Date: Sat, 19 Apr 2008 18:49:47 +0200 [thread overview]
Message-ID: <20080419164628.GA2214@elf.ucw.cz> (raw)
In-Reply-To: <84989B1A-CC23-4E81-B2E2-06E5FA01612E@holtmann.org>
Hi!
>> ok... But as long as the old code is buildable and installable, we should
>> fix bugs in it?
>
> I am okay with it and happy to accept any fixes, but to be quite honest,
> that this driver still works is in some cases pure luck. Doing the URB
> handling by ourself is really simply plain work. No excuses here and parts
> of it is my fault. I know that. Hence I started a new implementation from
> scratch.
Ok, so I guess this is good idea... (I'd prefer previous race patch to
still be applied; but driver is broken even with that fix...)
I thought about adding && BROKEN to Kconfig...
---
hci_usb is fatally broken, document it as such.
Signed-off-by: Pavel Machek <pavel@suse.cz>
diff --git a/drivers/bluetooth/Kconfig b/drivers/bluetooth/Kconfig
index 075598e..20d9279 100644
--- a/drivers/bluetooth/Kconfig
+++ b/drivers/bluetooth/Kconfig
@@ -3,13 +3,16 @@ menu "Bluetooth device drivers"
depends on BT
config BT_HCIUSB
- tristate "HCI USB driver"
+ tristate "HCI USB driver (dangerous, use alternate driver below)"
depends on USB
help
Bluetooth HCI USB driver.
This driver is required if you want to use Bluetooth devices with
USB interface.
+ Unfortunately, locking in this driver is fatally broken; it will
+ corrupt memory on surprise disconnect and during resume.
+
Say Y here to compile support for Bluetooth USB devices into the
kernel or say M to compile it as module (hci_usb).
diff --git a/drivers/bluetooth/hci_usb.c b/drivers/bluetooth/hci_usb.c
index 192522e..6cc96b4 100644
--- a/drivers/bluetooth/hci_usb.c
+++ b/drivers/bluetooth/hci_usb.c
@@ -1,8 +1,22 @@
-/*
+/*
+
+ This driver has fatally broken locking.
+
+ DO NOT USE.
+
+ See btusb.c for cleaner / shorter / actually working driver.
+
+
+
+
+
+
+
+
+
HCI USB driver for Linux Bluetooth protocol stack (BlueZ)
Copyright (C) 2000-2001 Qualcomm Incorporated
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
-
Copyright (C) 2003 Maxim Krasnyansky <maxk@qualcomm.com>
This program is free software; you can redistribute it and/or modify
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-19 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 20:46 [patch 3/3] hci_usb.h: fix hard-to-trigger race akpm
2008-04-18 21:10 ` Marcel Holtmann
[not found] ` <55DEC459-2D49-4366-88CC-21E9CA6783DC-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2008-04-18 21:21 ` Andrew Morton
[not found] ` <20080418142153.4e0eb83b.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-04-18 22:41 ` David Miller
2008-04-19 1:25 ` Marcel Holtmann
2008-04-19 16:49 ` Pavel Machek [this message]
2008-04-19 17:40 ` [patch] document hci_usb as broken Marcel Holtmann
2008-04-19 17:57 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080419164628.GA2214@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).