From: Andrey Smirnov <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e2324f: input/device: Fix off by one report descriptor siz...
Date: Fri, 05 Dec 2025 18:51:22 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1031026/000000-e2324f@github.com> (raw)
Branch: refs/heads/1031026
Home: https://github.com/bluez/bluez
Commit: e2324f7a87cdbc4c4f95882f841e560bd331327a
https://github.com/bluez/bluez/commit/e2324f7a87cdbc4c4f95882f841e560bd331327a
Author: Andrey Smirnov <andrew.smirnov@gmail.com>
Date: 2025-12-06 (Sat, 06 Dec 2025)
Changed paths:
M profiles/input/device.c
Log Message:
-----------
input/device: Fix off by one report descriptor size error
Due to the way we handle SDP strings internally BlueZ ends up
including and artifically added 0x00 into the report descriptor it
passes on to UHID. This results in kernel error messages like
[371225.240843] microsoft 0005:045E:02FD.0019: unknown main item tag 0x0
or
[367200.458679] playstation 0005:054C:0CE6.0014: unknown main item tag 0x0
The error is ignored by the kernel's report parser, so this is benign,
but for the sake of correctness, let's not supply bogus data in the
first place.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-12-06 2:51 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/1031026/000000-e2324f@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