Luiz Augusto von Dentz 172d277f82 Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ ... BugLink: https://bugs.launchpad.net/bugs/2073621 [ Upstream commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 ] This removes the bogus check for max > hcon->le_conn_max_interval since the later is just the initial maximum conn interval not the maximum the stack could support which is really 3200=4000ms. In order to pass GAP/CONN/CPUP/BV-05-C one shall probably enter values of the following fields in IXIT that would cause hci_check_conn_params to fail: TSPX_conn_update_int_min TSPX_conn_update_int_max TSPX_conn_update_peripheral_latency TSPX_conn_update_supervision_timeout Link: https://github.com/bluez/bluez/issues/847 Fixes: e4b019515f95 ("Bluetooth: Enforce validation on max value of connection interval") Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org> Signed-off-by: Portia Stephens <portia.stephens@canonical.com> Signed-off-by: Roxana Nicolescu <roxana.nicolescu@canonical.com>		2024-08-02 16:16:15 +02:00
..
bluetooth.h	Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks	2022-09-16 11:00:03 +02:00
hci.h	…
hci_core.h	Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ	2024-08-02 16:16:15 +02:00
hci_mon.h	Bluetooth: hci_sock: Correctly bounds check and pad HCI_MON_NEW_INDEX name	2024-01-05 14:29:59 +01:00
hci_sock.h	…
l2cap.h	Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put	2022-09-16 11:00:06 +02:00
mgmt.h	…
rfcomm.h	…
sco.h	…