[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <BBDABF4D-E4CC-49D7-ADCF-6913B2DE9FF0@holtmann.org>
Date: Wed, 11 Mar 2020 15:50:56 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: Howard Chung <howardchung@...gle.com>
Cc: Bluez mailing list <linux-bluetooth@...r.kernel.org>,
ChromeOS Bluetooth Upstreaming
<chromeos-bluetooth-upstreaming@...omium.org>,
"David S. Miller" <davem@...emloft.net>,
Johan Hedberg <johan.hedberg@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>
Subject: Re: [Bluez PATCH v1] Bluetooth: L2CAP: handle l2cap config request
during open state
Hi Howard,
> According to Core Spec Version 5.2 | Vol 3, Part A 6.1.5,
> the incoming L2CAP_ConfigReq should be handled during
> OPEN state.
>
> Signed-off-by: Howard Chung <howardchung@...gle.com>
>
> ---
>
> net/bluetooth/l2cap_core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 697c0f7f2c1a..5e6e35ab44dd 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -4300,7 +4300,8 @@ static inline int l2cap_config_req(struct l2cap_conn *conn,
> return 0;
> }
>
> - if (chan->state != BT_CONFIG && chan->state != BT_CONNECT2) {
> + if (chan->state != BT_CONFIG && chan->state != BT_CONNECT2 &&
> + chan->state != BT_CONNECTED) {
> cmd_reject_invalid_cid(conn, cmd->ident, chan->scid,
> chan->dcid);
> goto unlock;
Any chance you can add a btmon trace excerpt for this to the commit message. It would be good to have the before and after here included.
Regards
Marcel
Powered by blists - more mailing lists