tree 171c7984eeaade72d57a325ee26d55e4408bbdd1
parent 2266d8886f64c66e0a4e61e3e1c19dbc27ed00d4
author Marcel Holtmann <marcel@holtmann.org> 1152870132 +0200
committer David S. Miller <davem@sunset.davemloft.net> 1153770265 -0700

[Bluetooth] Correct RFCOMM channel MTU for broken implementations

Some Bluetooth RFCOMM implementations try to negotiate a bigger channel
MTU than we can support for a particular session. The maximum MTU for
a RFCOMM session is limited through the L2CAP layer. So if the other
side proposes a channel MTU that is bigger than the underlying L2CAP
MTU, we should reduce it to the L2CAP MTU of the session minus five
bytes for the RFCOMM headers.

Signed-off-by: Marcel Holtmann <marcel@holtmann.org>