| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 14 Nov 2012 16:30:44 -0500 (EST) From: David Miller <davem@...emloft.net> To: gustavo@...ovan.org Cc: ben@...adent.org.uk, linux-kernel@...r.kernel.org, stable@...r.kernel.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, ulisses@...fusion.mobi, marcel@...tmann.org, padovan@...fusion.mobi Subject: Re: [ 01/82] Bluetooth: Always compile SCO and L2CAP in Bluetooth Core From: Gustavo Padovan <gustavo@...ovan.org> Date: Wed, 14 Nov 2012 19:24:26 -0200 > Hi Ben, > > * Ben Hutchings <ben@...adent.org.uk> [2012-11-14 05:39:34 +0000]: > >> 3.2-stable review patch. If anyone has any objections, please let me know. >> >> ------------------ >> >> From: Ulisses Furquim <ulisses@...fusion.mobi> >> >> commit f1e91e1640d808d332498a6b09b2bcd01462eff9 upstream. >> >> The handling of SCO audio links and the L2CAP protocol are essential to >> any system with Bluetooth thus are always compiled in from now on. > > I wonder if this could not break any kind of script or code people have that > refer directly to the sco and l2cap modules. Also I don't see this change as > really necessary for 3.2. Agreed, I wish this had not been merged into -stable, I would have never submitted a patch like this myself. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists