Bluetooth: L2CAP: Fix handling fragmented length
authorLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
Wed, 13 Jan 2021 23:28:58 +0000 (15:28 -0800)
committerMarcel Holtmann <marcel@holtmann.org>
Mon, 25 Jan 2021 18:26:33 +0000 (19:26 +0100)
commit4d7ea8ee90e42fc75995f6fb24032d3233314528
tree05b5d1b68a055ba81fcb77a660046453ea6c7adf
parent5ff20cbe6752a5bc06ff58fee8aa11a0d5075819
Bluetooth: L2CAP: Fix handling fragmented length

Bluetooth Core Specification v5.2, Vol. 3, Part A, section 1.4, table
1.1:

 'Start Fragments always either begin with the first octet of the Basic
  L2CAP header of a PDU or they have a length of zero (see [Vol 2] Part
  B, Section 6.6.2).'

Apparently this was changed by the following errata:

https://www.bluetooth.org/tse/errata_view.cfm?errata_id=10216

Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
include/net/bluetooth/l2cap.h
net/bluetooth/l2cap_core.c