From: Kevin Dewald <kevin@simpleble.org>
To: linux-bluetooth@vger.kernel.org
Cc: Kevin Dewald <kevin@simpleble.org>
Subject: [PATCH BlueZ 0/3] emulator: Fix extended advertising report types
Date: Mon, 5 Oct 2026 09:21:14 -0700 [thread overview]
Message-ID: <20261005162117.4606-1-kevin@simpleble.org> (raw)
btdev sends the wrong Event_Type in two of the LE Extended Advertising
Reports it generates for an advertising set:
- the scan response to non-legacy scannable advertising is reported
with Event_Type 0x0000 instead of 0x000a
- with more than one active scanner, every scanner after the first gets
the advertisement reported as a scan response
The first patch removes le_ext_adv_type, which sits next to this code
and has been unused since advertising sets got their own struct.
I reproduced both with a small test driving an advertiser and two
scanners in-process. On master it shows:
scannable set: scan response 0x0000, expected 0x000a
two scanners: scanner 1 adv 0x001b, expected 0x0013
I can send it as a unit test if that would be useful.
mgmt-tester, iso-tester and smp-tester give the same results with and
without the series, apart from LL Privacy tests that fail
intermittently on both.
Kevin Dewald (3):
emulator: Remove unused le_ext_adv_type
emulator: Fix extended scan response Event_Type
emulator: Fix report type after a scan response
emulator/btdev.c | 37 ++++++-------------------------------
1 file changed, 6 insertions(+), 31 deletions(-)
--
2.54.0 (Apple Git-157)
next reply other threads:[~2026-10-05 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 16:21 Kevin Dewald [this message]
2026-10-05 16:21 ` [PATCH BlueZ 1/3] emulator: Remove unused le_ext_adv_type Kevin Dewald
2026-10-05 20:12 ` emulator: Fix extended advertising report types bluez.test.bot
2026-10-05 16:21 ` [PATCH BlueZ 2/3] emulator: Fix extended scan response Event_Type Kevin Dewald
2026-10-05 16:21 ` [PATCH BlueZ 3/3] emulator: Fix report type after a scan response Kevin Dewald
2026-10-07 18:40 ` [PATCH BlueZ 0/3] emulator: Fix extended advertising report types 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=20261005162117.4606-1-kevin@simpleble.org \
--to=kevin@simpleble.org \
--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