On Thu, Mar 29, 2012 at 08:22:51AM -0700, Greg KH wrote: > On Thu, Mar 29, 2012 at 11:55:04AM -0300, Gustavo Padovan wrote: > > Please include commit b7d05bad1c10a363b6b99f66ac1fa76b6892e618 into stable > > trees. It fixes a serious Bluetooth issue. > > > > Author: Peter Hurley <[email protected]> > > Date: Fri Jan 13 15:11:30 2012 +0100 > > > > Bluetooth: Fix l2cap conn failures for ssp devices > > > > Commit 330605423c fixed l2cap conn establishment for non-ssp remote > > devices by not setting HCI_CONN_ENCRYPT_PEND every time conn security > > is tested (which was always returning failure on any subsequent > > security checks). > > > > However, this broke l2cap conn establishment for ssp remote devices > > when an ACL link was already established at SDP-level security. This > > fix ensures that encryption must be pending whenever authentication > > is also pending. > > > > Signed-off-by: Peter Hurley <[email protected]> > > Tested-by: Daniel Wagner <[email protected]> > > Acked-by: Marcel Holtmann <[email protected]> > > Signed-off-by: Johan Hedberg <[email protected]> > > This patch doesn't apply to the 3.3 kernel tree, but it applies to older > releases. Should it not go into 3.3? If it should, can you please > provide a backported version of it?
And it breaks the build in the 3.0 and 3.2-stable kernels, so it doesn't work there either. Please test out patches that you want applied, otherwise it wastes other people's time :( greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
