Hi, On Sat, May 12, 2012, Gustavo Padovan wrote: > In my point of view there are two commits there that are really necessary: > > Gustavo Padovan (2): > Bluetooth: report the right security level in getsockopt > > Johan Hedberg (2): > Bluetooth: mgmt: Fix device_connected sending order > > They fix a userspace breakage caused by: > > Author: Marcel Holtmann <marcel@xxxxxxxxxxxx> > Date: Mon Feb 20 21:24:37 2012 +0100 > > Bluetooth: Always enable management interface > > The management interface API has reached stable version 1.0 and thus > it can now be always enabled. All future changes will be made backwards > compatible. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > > > This cause no crash, but it make bluetooth keyboards stop to work with Linux. > This a serious breakage IMO. I really would like to see at least these two > patches in. The other fixes can wait. I'd just like to add some further background since I don't think it's that obvious how these are regression fixes: The device_connected fix should be quite self-explanatory, but it's actually a wider issue than just for keyboards. All profiles that do incoming connection authorization (e.g. headsets) will break without it with specific hardware. The reason it wasn't caught earlier is that it only occurs with specific Bluetooth adapters. As for the security level patch, this fixes L2CAP socket based security level elevation during a connection. The HID profile needs this (for keyboards) and it is the only way to achieve the security level elevation when using the management interface to talk to the kernel (hence the management enabling patch being the one that exposes this issue). Johan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
