summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/l2cap.c
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2009-02-17 21:49:33 +0100
committerMarcel Holtmann <marcel@holtmann.org>2009-02-27 06:14:48 +0100
commit37e62f5516cfb210e64fe53457932df4341b0ad1 (patch)
tree7bf4d14be4acbc9f9198d5dedb5ed5fb9badb729 /net/bluetooth/l2cap.c
parentBluetooth: Disallow usage of L2CAP CID setting for now (diff)
downloadlinux-37e62f5516cfb210e64fe53457932df4341b0ad1.tar.xz
linux-37e62f5516cfb210e64fe53457932df4341b0ad1.zip
Bluetooth: Fix RFCOMM usage of in-kernel L2CAP sockets
The CID value of L2CAP sockets need to be set to zero. All userspace applications do this via memset() on the sockaddr_l2 structure. The RFCOMM implementation uses in-kernel L2CAP sockets and so it has to make sure that l2_cid is set to zero. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth/l2cap.c')
0 files changed, 0 insertions, 0 deletions