From: "ooonea.eth" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] de087b: input: Reset report map state on detach
Date: Fri, 25 Sep 2026 11:59:53 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1173956/000000-494109@github.com> (raw)
Branch: refs/heads/1173956
Home: https://github.com/bluez/bluez
Commit: de087bad140bfa2bf382787f9c2e181cff9e45c4
https://github.com/bluez/bluez/commit/de087bad140bfa2bf382787f9c2e181cff9e45c4
Author: Giuseppe Piscitelli <35407790+ooonea@users.noreply.github.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M profiles/input/hog-lib.c
Log Message:
-----------
input: Reset report map state on detach
read_report_map() leaves report_map_id set after a failed read. Detach
cancels queued GATT operations but retains that ID, so a later attach
cannot request the report map again and never creates the UHID device.
Clear the ID when cancelling GATT operations on detach. This also lets
a reconnect retry a read that was still pending at disconnection.
A socketpair reproducer fails to read the map after either an ATT error
or cancellation before this change; both cases create UHID afterwards.
The existing HoG and UHID unit tests also pass.
Assisted-by: OpenAI Codex:gpt-6
Commit: 4941097ab417c71166859916d7b9dfa0f2695f5f
https://github.com/bluez/bluez/commit/4941097ab417c71166859916d7b9dfa0f2695f5f
Author: Giuseppe Piscitelli <35407790+ooonea@users.noreply.github.com>
Date: 2026-09-25 (Fri, 25 Sep 2026)
Changed paths:
M Makefile.am
M unit/test-hog.c
Log Message:
-----------
unit: Test HoG report map reads after reconnect
Exercise reconnect after an ATT error and after cancelling a pending
Report Map read. Require a fresh read and validate the resulting
UHID_CREATE2 descriptor on a simulated transport.
Stub Bluetooth address lookup for the Unix socketpair fixture. Both
cases fail without resetting report_map_id on detach.
Assisted-by: OpenAI Codex:gpt-6
Compare: https://github.com/bluez/bluez/compare/de087bad140b%5E...4941097ab417
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-25 18:59 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/1173956/000000-494109@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