Culprit commits are: b783fbc Bluetooth: Refuse peer L2CAP address reading when not connected 35364c9 Bluetooth: Refuse peer RFCOMM address reading when not connected The reason these break things is that they limit peer address checking to connected sockets, btio's get_peers() function is calling both getsockname() and getpeername(), bailing out if either fails, before checking what option is being checked for. Smells more like a bluetoothd fix, but I don't like the idea of earlier versions of bluetoothd breaking on newer kernels. Scott -- Scott James Remnant | Chrome OS Systems | keybuk@xxxxxxxxxx | Google -- 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
