From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 0/4] Add 6lowpan-tester
Date: Mon, 6 Oct 2025 01:17:38 +0300 [thread overview]
Message-ID: <cover.1759702519.git.pav@iki.fi> (raw)
Make a basic tester for the net/bluetooth/6lowpan.c implementation.
This module doesn't look like it's much used and locking around
l2cap_chan / hci_conn there looks suspicious, so probably some tests are
useful.
Here just simple connection / disconnection and packet RX tests are
added. Some issues appear to be there:
Client Recv Raw - Success
-> kernel panic (kernel BUG at net/core/skbuff.c:212!)
Client Connect - Disable
-> lockdep splats
Pauli Virtanen (4):
bthost: handle L2CAP_DISCONN_RSP and remove l2cap_conns
bthost: handle L2CAP_FLOW_CONTROL_CREDIT_IND
tools: add 6lowpan-tester
doc: enable 6lowpan in tester.config and explain in test-runner.rst
Makefile.tools | 12 +-
doc/test-runner.rst | 10 +
doc/tester.config | 5 +
emulator/bthost.c | 93 +++++-
emulator/bthost.h | 6 +-
tools/6lowpan-tester.c | 657 +++++++++++++++++++++++++++++++++++++++++
tools/l2cap-tester.c | 3 +-
7 files changed, 782 insertions(+), 4 deletions(-)
create mode 100644 tools/6lowpan-tester.c
--
2.51.0
next reply other threads:[~2025-10-05 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 22:17 Pauli Virtanen [this message]
2025-10-05 22:17 ` [PATCH BlueZ 1/4] bthost: handle L2CAP_DISCONN_RSP and remove l2cap_conns Pauli Virtanen
2025-10-05 23:42 ` Add 6lowpan-tester bluez.test.bot
2025-10-05 22:17 ` [PATCH BlueZ 2/4] bthost: handle L2CAP_FLOW_CONTROL_CREDIT_IND Pauli Virtanen
2025-10-05 22:17 ` [PATCH BlueZ 3/4] tools: add 6lowpan-tester Pauli Virtanen
2025-10-13 17:20 ` Luiz Augusto von Dentz
2025-10-05 22:17 ` [PATCH BlueZ 4/4] doc: enable 6lowpan in tester.config and explain in test-runner.rst Pauli Virtanen
2025-10-13 17:40 ` [PATCH BlueZ 0/4] Add 6lowpan-tester patchwork-bot+bluetooth
2025-10-13 19:00 ` patchwork-bot+bluetooth
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=cover.1759702519.git.pav@iki.fi \
--to=pav@iki.fi \
--cc=linux-bluetooth@vger.kernel.org \
/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