Hi, On Mon, Nov 22, 2010, Gustavo F. Padovan wrote: > > The other fixes are larger than I would like to see. What is the > > effect of the bug? Does the Bluetooth controller stop completely? > > Does it cause a crash? > > > > Is this a newly-introduced bug? Or one that has been around for > > a while? > > No, it is not serious like that. By not having this patch we won't have > the remote name request command during connection setup, The remote name > request was done by bluetoothd, but we already removed it from > userspace. It is not a really big problem once we also cache the remote > devices names in bluetoothd. > So I'm seeing no way to convince you tou pull this patch (actually I'm > now also covinced to queue this to bluetooth-next). I'll sent a new > pull request soon, after wait some time for new patches. IIRC the symptom that prompted the initial investigation was the failure to properly connect to one specific Bluetooth headset. After discussions with Marcel the conculsion was to move more control of these commands to the kernel side. OTOH, this is certainly not the first time a BT controller chokes up when receiving too many commands at the same time (I've seen this several times during the last 8 years or so that I've been involved with Bluetooth). Anyway, I agree that this might be better suited for bluetooth-next. Johan -- 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
