From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e19c77: emulator: btvirt: check pkt lengths, don't get stu...
Date: Thu, 14 May 2026 12:10:46 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/c47895-48cb22@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e19c771841e9017326103a8d8e8139b2374ffe19
https://github.com/bluez/bluez/commit/e19c771841e9017326103a8d8e8139b2374ffe19
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M emulator/server.c
Log Message:
-----------
emulator: btvirt: check pkt lengths, don't get stuck on malformed
Don't try to parse packet before whole header is received.
If received data has unknown packet type, reset buffer so that we don't
get stuck.
Commit: 5ee43f9993ddb6f42a281b513885d9f0eb9f9a05
https://github.com/bluez/bluez/commit/5ee43f9993ddb6f42a281b513885d9f0eb9f9a05
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M emulator/main.c
Log Message:
-----------
emulator: btvirt: allow specifying where server unix sockets are made
Make --server to take optional path name where to create the various
server sockets.
Commit: cc077e4a12dd4d7e3eeeacc1a658416d105f7f39
https://github.com/bluez/bluez/commit/cc077e4a12dd4d7e3eeeacc1a658416d105f7f39
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M emulator/server.c
Log Message:
-----------
emulator: btvirt: support SCO data packets
Support also SCO data packets in btvirt.
Commit: f1a303e1d07a715db6d7cadcf757e02f41c0468b
https://github.com/bluez/bluez/commit/f1a303e1d07a715db6d7cadcf757e02f41c0468b
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
emulator: btdev: clear more state on Reset
On controller Reset command, initialize most fields in struct btdev to
zero, similarly to the state just after btdev_create().
This excludes some fields like command bitmasks, which hciemu may have
adjusted.
To make this easier, add struct_group() macro similar to what kernel
uses.
Commit: ff2ecb82e4c38849112aebe0ac9b27af03a2284d
https://github.com/bluez/bluez/commit/ff2ecb82e4c38849112aebe0ac9b27af03a2284d
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: enable path argument for --unix
Allow specifying the path for the controller socket to be used.
Commit: 82c635c879bf66b6efe36d4efb184c02d9c15dc1
https://github.com/bluez/bluez/commit/82c635c879bf66b6efe36d4efb184c02d9c15dc1
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: Add -o/--option option
Allow passing arbitrary arguments to QEMU.
Commit: 1929b3a99d2f2149fd9fb0e2cb473fcdce4da63a
https://github.com/bluez/bluez/commit/1929b3a99d2f2149fd9fb0e2cb473fcdce4da63a
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: allow source tree root for -k
Allow passing source tree root for -k option, look up kernel below it.
Commit: 908c14fc3abb96b553821aa81c88f4604af91379
https://github.com/bluez/bluez/commit/908c14fc3abb96b553821aa81c88f4604af91379
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M tools/test-runner.c
Log Message:
-----------
test-runner: use virtio-serial for implementing -u device forwarding
Using pci-serial to forward eg. btvirt sockets is unreliable, as qemu or
kernel seems to be sometimes dropping part of the sent data or insert
spurious \0 bytes, leading to sporadic errors like:
kernel: Bluetooth: hci0: command 0x0c52 tx timeout
kernel: Bluetooth: hci0: Opcode 0x0c52 failed: -110
btvirt: packet error, unknown type: 0
This appears to occur most often when host system is under load, e.g.
due to multiple test-runners running at the same time. The problem is
not specific to btvirt, but seems to be in the qemu serial device layer
vs. kernel interaction.
Change test-runner to use virtserialport to forward the btvirt
connection inside the VM, as virtio-serial doesn't appear to have these
problems.
Commit: 7856de4d69d66d360616ddfd071171358e831ea1
https://github.com/bluez/bluez/commit/7856de4d69d66d360616ddfd071171358e831ea1
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M doc/ci.config
M doc/test-runner.rst
M doc/tester.config
Log Message:
-----------
doc: enable CONFIG_VIRTIO_CONSOLE in tester config
Enable kernel option that allows using -device virtserialport in qemu.
This is easier to make work reliably than pci-serial channel.
Commit: 48cb22a572c7001bf4377cec761702857680f4c0
https://github.com/bluez/bluez/commit/48cb22a572c7001bf4377cec761702857680f4c0
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-14 (Thu, 14 May 2026)
Changed paths:
M doc/ci.config
M doc/test-runner.rst
M doc/tester.config
Log Message:
-----------
doc: enable KVM paravirtualization & clock support in tester kernel config
Enable KVM guest and PTP options in tester kernel config.
This allows synchronizing tester VM guest with host clock, needed for
testers that want to compare timestamps outside the VM guest.
Compare: https://github.com/bluez/bluez/compare/c4789506455f...48cb22a572c7
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-05-14 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/c47895-48cb22@github.com \
--to=noreply@github.com \
--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