From: raghava447 <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 27eb49: shared/hci: Avoid redundant BPF filter updates on ...
Date: Tue, 09 Jun 2026 09:37:41 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/622a46-912d67@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 27eb493882aed659339579adb29ca99b61042379
https://github.com/bluez/bluez/commit/27eb493882aed659339579adb29ca99b61042379
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M src/shared/hci.c
Log Message:
-----------
shared/hci: Avoid redundant BPF filter updates on duplicate events
Skip updating the BPF socket filter in bt_hci_register and
bt_hci_register_subevent when the event/subevent is already
registered, since it is already part of the filter.
Similarly, skip updating the filter in bt_hci_unregister and
bt_hci_unregister_subevent when other handlers for the same
event/subevent still remain in the queue.
This avoids unnecessary setsockopt(SO_ATTACH_FILTER) calls when
multiple handlers are registered for the same event code.
Commit: 9320e1cb47494aa67cf86bc0dda1913f4e489478
https://github.com/bluez/bluez/commit/9320e1cb47494aa67cf86bc0dda1913f4e489478
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-08 (Mon, 08 Jun 2026)
Changed paths:
M src/shared/hci.c
Log Message:
-----------
shared/hci: Debounce SO_ATTACH_FILTER with timeout_add(0)
Coalesce multiple BPF filter updates into a single SO_ATTACH_FILTER
setsockopt call by deferring the update to the next event loop
iteration using timeout_add(0, ...).
When bt_hci_register_event or bt_hci_register_subevent is called
multiple times in succession (e.g. from bt_rap_attach_hci), each call
previously triggered a full filter rebuild and setsockopt. Now,
schedule_evt_filter() simply marks a pending update which fires once
in filter_timeout() after all synchronous registrations complete.
Commit: 8bc6dd81c9c21137f0b63ac59db49c26b6af6c65
https://github.com/bluez/bluez/commit/8bc6dd81c9c21137f0b63ac59db49c26b6af6c65
Author: raghu447 <raghavendra.rao@collabora.com>
Date: 2026-06-09 (Tue, 09 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: add ASE Control Point error responses
These changes are required to Pass BAP/USR/SPE/BI-01[5]-C tests.
Commit: 912d67d1d3a46f5ef946eec2dbe310b97247f085
https://github.com/bluez/bluez/commit/912d67d1d3a46f5ef946eec2dbe310b97247f085
Author: raghu447 <raghavendra.rao@collabora.com>
Date: 2026-06-09 (Tue, 09 Jun 2026)
Changed paths:
M unit/test-bap.c
Log Message:
-----------
unit/bap: add SPE tests
Add unit tests for the PTS BAP/USR/SPE/BI-01[5]-C tests.
Compare: https://github.com/bluez/bluez/compare/622a46ebcd72...912d67d1d3a4
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-09 16:37 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/622a46-912d67@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