Bluetooth: Fix accepting early data on fixed channels
authorJohan Hedberg <johan.hedberg@intel.com>
Mon, 16 Feb 2015 09:42:11 +0000 (11:42 +0200)
committerMarcel Holtmann <marcel@holtmann.org>
Mon, 16 Feb 2015 15:49:36 +0000 (16:49 +0100)
commit315917e0a6d552a33f774935d8897ec1697605dd
treec1c3f68702d9e13d72dfe0ad061f49631399a044
parent035a07d5df7003bc6954f0aa42174416b775021c
Bluetooth: Fix accepting early data on fixed channels

On BR/EDR the L2CAP channel instances for fixed channels have so far
been marked as ready only once the L2CAP information req/rsp procedure
is complete and we have the fixed channel mask. This could however lead
to data being dropped if we receive it on the channel before knowing the
remote mask.

Since it is valid for a remote to send data this early, simply assume
that the channel is supported when we receive data on it. So far this
hasn't been noticed much because of limited use of fixed channels on
BR/EDR, but e.g. with SMP over BR/EDR this is already now visible with
automated tests failing randomly.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
net/bluetooth/l2cap_core.c