Linux bluetooth development
 help / color / mirror / Atom feed
From: "ooonea.eth" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] ad9f35: input: Reset report map state on detach
Date: Fri, 25 Sep 2026 17:38:36 -0700	[thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1174115/000000-ad9f35@github.com> (raw)

  Branch: refs/heads/1174115
  Home:   https://github.com/bluez/bluez
  Commit: ad9f353d3126394de02a19abc185a83c96127d3a
      https://github.com/bluez/bluez/commit/ad9f353d3126394de02a19abc185a83c96127d3a
  Author: Giuseppe Piscitelli <35407790+ooonea@users.noreply.github.com>
  Date:   2026-09-26 (Sat, 26 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



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications

                 reply	other threads:[~2026-09-26  0:38 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/1174115/000000-ad9f35@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