Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8183b775 authored by Andrei Emeltchenko's avatar Andrei Emeltchenko Committed by Gustavo Padovan
Browse files

Bluetooth: fix MTU L2CAP configuration parameter 



When receiving L2CAP negative configuration response with respect
to MTU parameter we modify wrong field. MTU here means proposed
value of MTU that the remote device intends to transmit. So for local
L2CAP socket it is pi->imtu.

Signed-off-by: default avatarAndrei Emeltchenko <andrei.emeltchenko@nokia.com>
Acked-by: default avatarVille Tervo <ville.tervo@nokia.com>
Signed-off-by: default avatarGustavo F. Padovan <padovan@profusion.mobi>
parent 8c462b60

net/bluetooth/l2cap.c

+3 −3
Original line number Diff line number Diff line
@@ -2771,10 +2771,10 @@ static int l2cap_parse_conf_rsp(struct sock *sk, void *rsp, int len, void *data, 
		case L2CAP_CONF_MTU:

			if (val < L2CAP_DEFAULT_MIN_MTU) {

				*result = L2CAP_CONF_UNACCEPT;

				pi->omtu = L2CAP_DEFAULT_MIN_MTU;

				pi->imtu = L2CAP_DEFAULT_MIN_MTU;

			} else

				pi->omtu = val;

			l2cap_add_conf_opt(&ptr, L2CAP_CONF_MTU, 2, pi->omtu);

				pi->imtu = val;

			l2cap_add_conf_opt(&ptr, L2CAP_CONF_MTU, 2, pi->imtu);

			break;



		case L2CAP_CONF_FLUSH_TO: