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>
This commit is contained in:
committed by
Marcel Holtmann
parent
5ff20cbe67
commit
4d7ea8ee90
@@ -207,6 +207,7 @@ struct l2cap_hdr {
|
||||
__le16 len;
|
||||
__le16 cid;
|
||||
} __packed;
|
||||
#define L2CAP_LEN_SIZE 2
|
||||
#define L2CAP_HDR_SIZE 4
|
||||
#define L2CAP_ENH_HDR_SIZE 6
|
||||
#define L2CAP_EXT_HDR_SIZE 8
|
||||
|
||||
Reference in New Issue
Block a user