From: Sungwoo Kim <happiness.sung.woo@gmail.com>
To: iam@sung-woo.kim
Cc: davem@davemloft.net, edumazet@google.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: [BUG 6 / 6] L2cap: Spec violations
Date: Thu, 17 Nov 2022 23:03:56 -0500 [thread overview]
Message-ID: <20221118040356.631678-1-git@sung-woo.kim> (raw)
In-Reply-To: <CAJNyHpKpDdps4=QHZ77zu4jfY-NNBcGUrw6UwjuBKfpuSuE__g@mail.gmail.com>
6. BT_DISCONN -> BT_CONNECTED by L2CAP_CONN_RSP
btmon log:
Bluetooth monitor ver 5.64
= Note: Linux version 6.1.0-rc2 (x86_64) 0.240003
= Note: Bluetooth subsystem version 2.22 0.240035
(...)
> ACL Data RX: Handle 200 flags 0x00 dlen 1033 #32 [hci0] 12.777814
invalid packet size (12 != 1033)
08 00 01 00 02 01 04 00 01 10 ff ff ............
@ MGMT Event: Device Connected (0x000b) plen 13 {0x0001} [hci0] 12.797646
BR/EDR Address: 10:AA:AA:AA:AA:AA (OUI 10-AA-AA)
Flags: 0x00000000
Data length: 0
@ MGMT Event: Device Connected (0x000b) plen 13 {0x0002} [hci0] 12.797646
BR/EDR Address: 10:AA:AA:AA:AA:AA (OUI 10-AA-AA)
Flags: 0x00000000
Data length: 0
> ACL Data RX: Handle 200 flags 0x00 dlen 2061 #33 [hci0] 12.778616
invalid packet size (16 != 2061)
0c 00 01 00 03 01 08 00 00 00 00 00 00 00 00 00 ................
> ACL Data RX: Handle 200 flags 0x00 dlen 2061 #34 [hci0] 12.778858
invalid packet size (16 != 2061)
0c 00 01 00 04 01 08 00 40 00 00 00 07 00 00 01 ........@.......
> ACL Data RX: Handle 200 flags 0x00 dlen 2061 #35 [hci0] 12.778882
invalid packet size (16 != 2061)
0c 00 01 00 04 01 08 00 40 00 00 00 07 02 00 00 ........@.......
> ACL Data RX: Handle 200 flags 0x00 dlen 1547 #36 [hci0] 12.778905
invalid packet size (14 != 1547)
0a 00 01 00 05 01 06 00 40 00 00 00 00 00 ........@.....
prev parent reply other threads:[~2022-11-18 4:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 3:52 [BUG 0 / 6] L2cap: Spec violations Sungwoo Kim
2022-11-18 3:55 ` [BUG 1 " Sungwoo Kim
2022-11-18 4:02 ` [BUG 2 " Sungwoo Kim
2022-11-18 4:02 ` [BUG 3 " Sungwoo Kim
2022-11-18 4:03 ` [BUG 4 " Sungwoo Kim
2022-11-18 4:03 ` [BUG 5 " Sungwoo Kim
2022-11-18 4:03 ` Sungwoo Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221118040356.631678-1-git@sung-woo.kim \
--to=happiness.sung.woo@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=iam@sung-woo.kim \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).