<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/net/bluetooth/l2cap.h, branch linux-3.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-01-01T20:51:03Z</updated>
<entry>
<title>Bluetooth: hidp: verify l2cap sockets</title>
<updated>2018-01-01T20:51:03Z</updated>
<author>
<name>David Herrmann</name>
</author>
<published>2013-04-05T12:57:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6b369a5d1ed6c5c04a76db01c21802e1ca11ec82'/>
<id>urn:sha1:6b369a5d1ed6c5c04a76db01c21802e1ca11ec82</id>
<content type='text'>
commit b3916db32c4a3124eee9f3742a2f4723731d7602 upstream.

We need to verify that the given sockets actually are l2cap sockets. If
they aren't, we are not supposed to access bt_sk(sock) and we shouldn't
start the session if the offsets turn out to be valid local BT addresses.

That is, if someone passes a TCP socket to HIDCONNADD, then we access some
random offset in the TCP socket (which isn't even guaranteed to be valid).

Fix this by checking that the socket is an l2cap socket.

Signed-off-by: David Herrmann &lt;dh.herrmann@gmail.com&gt;
Acked-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Gustavo Padovan &lt;gustavo.padovan@collabora.co.uk&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Use miliseconds for L2CAP channel timeouts</title>
<updated>2011-11-07T19:19:04Z</updated>
<author>
<name>Andrzej Kaczmarek</name>
</author>
<published>2011-11-07T19:19:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f3f668b0ef4399b67e60e4c10a30099d630a6206'/>
<id>urn:sha1:f3f668b0ef4399b67e60e4c10a30099d630a6206</id>
<content type='text'>
Timers set by __set_chan_timer() should use miliseconds instead of
jiffies. Commit 942ecc9c4643db5ce071562e0a23f99464d6b461 updated
l2cap_set_timer() so it expects timeout to be specified in msecs
instead of jiffies. This makes timeouts unreliable when CONFIG_HZ
is not set to 1000.

Signed-off-by: Andrzej Kaczmarek &lt;andrzej.kaczmarek@tieto.com&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Perform L2CAP SDU reassembly without copying data</title>
<updated>2011-09-27T21:16:18Z</updated>
<author>
<name>Mat Martineau</name>
</author>
<published>2011-07-22T21:54:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84084a3197a9fdec10fa542c0df11928a784e7fc'/>
<id>urn:sha1:84084a3197a9fdec10fa542c0df11928a784e7fc</id>
<content type='text'>
Use sk_buff fragment capabilities to link together incoming skbs
instead of allocating a new skb for reassembly and copying.

The new reassembly code works equally well for ERTM and streaming
mode, so there is now one reassembly function instead of two.

Signed-off-by: Mat Martineau &lt;mathewm@codeaurora.org&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Move SMP fields to a separate structure</title>
<updated>2011-09-21T15:58:12Z</updated>
<author>
<name>Vinicius Costa Gomes</name>
</author>
<published>2011-09-05T17:31:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1c1def09c446aae441410b70e6439ffe44dee866'/>
<id>urn:sha1:1c1def09c446aae441410b70e6439ffe44dee866</id>
<content type='text'>
The objective is to make the core to have as little as possible
information about SMP procedures and logic. Now, all the SMP
specific information is hidden from the core.

Signed-off-by: Vinicius Costa Gomes &lt;vinicius.gomes@openbossa.org&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Fixes l2cap "command reject" reply according to spec</title>
<updated>2011-07-11T04:43:25Z</updated>
<author>
<name>Ilia Kolomisnky</name>
</author>
<published>2011-07-10T05:47:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e2fd318e3a9208245ee1041f6d413c8593fba29d'/>
<id>urn:sha1:e2fd318e3a9208245ee1041f6d413c8593fba29d</id>
<content type='text'>
There can 3 reasons for the "command reject" reply produced
by the stack. Each such reply should be accompanied by the
relevand data ( as defined in spec. ). Currently there is one
instance of "command reject" reply with reason "invalid cid"
wich is fixed. Also, added clean-up definitions related to the
"command reject" replies.

Signed-off-by: Ilia Kolomisnky &lt;iliak@ti.com&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Remove L2CAP busy queue</title>
<updated>2011-07-07T18:29:06Z</updated>
<author>
<name>Mat Martineau</name>
</author>
<published>2011-07-07T16:39:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fadd192e81b0a8d8086531b8c11bd88b311b68c2'/>
<id>urn:sha1:fadd192e81b0a8d8086531b8c11bd88b311b68c2</id>
<content type='text'>
The ERTM receive buffer is now handled in a way that does not require
the busy queue and the associated polling code.

Signed-off-by: Mat Martineau &lt;mathewm@codeaurora.org&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Use event-driven approach for handling ERTM receive buffer</title>
<updated>2011-07-07T18:28:56Z</updated>
<author>
<name>Mat Martineau</name>
</author>
<published>2011-07-07T16:39:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e328140fdacbba43292a59a22fb55d9185288318'/>
<id>urn:sha1:e328140fdacbba43292a59a22fb55d9185288318</id>
<content type='text'>
This change moves most L2CAP ERTM receive buffer handling out of the
L2CAP core and in to the socket code.  It's up to the higher layer
(the socket code, in this case) to tell the core when its buffer is
full or has space available.  The recv op should always accept
incoming ERTM data or else the connection will go down.

Within the socket layer, an skb that does not fit in the socket
receive buffer will be temporarily stored.  When the socket is read
from, that skb will be placed in the receive buffer if possible.  Once
adequate buffer space becomes available, the L2CAP core is informed
and the ERTM local busy state is cleared.

Receive buffer management for non-ERTM modes is unchanged.

Signed-off-by: Mat Martineau &lt;mathewm@codeaurora.org&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Use bit operations on conn_state</title>
<updated>2011-06-16T21:57:15Z</updated>
<author>
<name>Gustavo F. Padovan</name>
</author>
<published>2011-06-11T00:28:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e2ab43536c53ba112a0adfb4c0dba286544c41f6'/>
<id>urn:sha1:e2ab43536c53ba112a0adfb4c0dba286544c41f6</id>
<content type='text'>
Instead of setting bits manually we use set_bit, test_bit, etc.
Also remove L2CAP_ prefix from macros.

Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: use bit operation on conf_state</title>
<updated>2011-06-16T21:57:14Z</updated>
<author>
<name>Gustavo F. Padovan</name>
</author>
<published>2011-06-10T20:02:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c1360a1cf35117d6f3898cb5183ce4349d06714c'/>
<id>urn:sha1:c1360a1cf35117d6f3898cb5183ce4349d06714c</id>
<content type='text'>
Instead of making the bit operations manually, we now use set_bit,
test_bit, etc.

Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
<entry>
<title>Bluetooth: Add key size checks for SMP</title>
<updated>2011-06-14T17:54:10Z</updated>
<author>
<name>Vinicius Costa Gomes</name>
</author>
<published>2011-06-14T16:37:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3158c50c33c1acddcfa3c57fab812435aa459750'/>
<id>urn:sha1:3158c50c33c1acddcfa3c57fab812435aa459750</id>
<content type='text'>
This patch implements a check in smp cmd pairing request and pairing
response to verify if encryption key maximum size is compatible in both
slave and master when SMP Pairing is requested. Keys are also masked to
the correct negotiated size.

Signed-off-by: Vinicius Costa Gomes &lt;vinicius.gomes@openbossa.org&gt;
Signed-off-by: Anderson Briglia &lt;anderson.briglia@openbossa.org&gt;
Signed-off-by: Gustavo F. Padovan &lt;padovan@profusion.mobi&gt;
</content>
</entry>
</feed>
