bluetooth: Properly clone LSM attributes to newly created child connections
authorPaul Moore <pmoore@redhat.com>
Fri, 7 Oct 2011 09:40:59 +0000 (09:40 +0000)
committerDavid S. Miller <davem@davemloft.net>
Wed, 19 Oct 2011 03:36:43 +0000 (23:36 -0400)
commit6230c9b4f8957c8938ee4cf2d03166d3c2dc89de
treeacb6aa03e5b34ab83c4945fdacefee66c5285af2
parent835acf5da239b91edb9f7ebe36516999e156e6ee
bluetooth: Properly clone LSM attributes to newly created child connections

The Bluetooth stack has internal connection handlers for all of the various
Bluetooth protocols, and unfortunately, they are currently lacking the LSM
hooks found in the core network stack's connection handlers.  I say
unfortunately, because this can cause problems for users who have have an
LSM enabled and are using certain Bluetooth devices.  See one problem
report below:

 * http://bugzilla.redhat.com/show_bug.cgi?id=741703

In order to keep things simple at this point in time, this patch fixes the
problem by cloning the parent socket's LSM attributes to the newly created
child socket.  If we decide we need a more elaborate LSM marking mechanism
for Bluetooth (I somewhat doubt this) we can always revisit this decision
in the future.

Reported-by: James M. Cape <jcape@ignore-your.tv>
Signed-off-by: Paul Moore <pmoore@redhat.com>
Acked-by: James Morris <jmorris@namei.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/bluetooth/l2cap_sock.c
net/bluetooth/rfcomm/sock.c
net/bluetooth/sco.c
security/security.c