From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215089] New: local struct uinput_event inconsistency with kernel y2038 safe struct input_event: AVRCP events vanish on 32-bit
Date: Sun, 21 Nov 2021 15:55:04 +0000 [thread overview]
Message-ID: <bug-215089-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215089
Bug ID: 215089
Summary: local struct uinput_event inconsistency with kernel
y2038 safe struct input_event: AVRCP events vanish on
32-bit
Product: Drivers
Version: 2.5
Kernel Version: 5.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: spam@ipik.org
Regression: No
Under bluez (up to 5.62) compiled with time64 support (like musl1.2 or possibly
newer glibc with __USE_TIME_BITS64) on 32-bit systems (x86 or armhf for
instance), AVRCP events just never show-up on input device.
Tools like evtest will not report any event upon bluetooth headset media button
keypress, whereas btmon sees them flowing through.
This bug does not hit x86-64 releases, only 32-bit are affected.
Issue has been discussed here [1], with a simple & replicable Alpinelinux 3.14
test case (based on musl 1.2).
Legacy local uinput_event struct might not play well with newer time64-aware
input_event kernel structure.
[1] https://github.com/bluez/bluez/issues/84#issuecomment-942155841
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-11-21 15:55 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=bug-215089-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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