From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220061] [REGRESSION, BISECTED] Multiple Bluetooth devices cannot be paired under Linux 6.14.4
Date: Thu, 08 May 2025 13:13:20 +0000 [thread overview]
Message-ID: <bug-220061-62941-JE4RGYOYPt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220061-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220061
--- Comment #16 from Artem S. Tashkinov (aros@gmx.com) ---
Strangely I don't see anything relevant queued for the stable.(In reply to Luiz
Von Dentz from comment #12)
> (In reply to Sandro Forster from comment #11)
> > I've tested v2 of the fix with a DualShock 4 v1 and v2 (the firmware is
> > probably the same, but just to be sure). Both had the same behavior.
> > Connecting failed on the first attempt, but every following connection
> > succeeded. When bluetooth is restarted, the first connection fails again.
> > Here is the output of btmon for a unsuccessful and successful connection
> > attempt. I've attached to logs above.
>
> I think that is because when you restart the daemon the link keys are
> reloaded and then their key size is lost in the process (for Classic, for LE
> the key size seem to be stored by the daemon), anyway I just spin a v3 to
> address this so if we don't know the key encryption size we use
> hdev->min_enc_key_size to satisfy l2cap_check_enc_key_size:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20250502202052.2802441-
> 1-luiz.dentz@gmail.com/
Strangely I don't see anything relevant queued for the stable.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-05-08 13:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 15:10 [Bug 220061] New: [REGRESSION, BISECTED] Multiple Bluetooth devices cannot be paired under Linux 6.14.4 bugzilla-daemon
2025-04-28 15:12 ` [Bug 220061] " bugzilla-daemon
2025-04-28 15:12 ` bugzilla-daemon
2025-04-28 17:58 ` bugzilla-daemon
2025-04-29 7:08 ` bugzilla-daemon
2025-04-29 12:08 ` bugzilla-daemon
2025-04-29 12:13 ` bugzilla-daemon
2025-04-29 14:13 ` bugzilla-daemon
2025-04-30 7:51 ` bugzilla-daemon
2025-05-01 6:06 ` bugzilla-daemon
2025-05-02 13:48 ` bugzilla-daemon
2025-05-02 18:29 ` bugzilla-daemon
2025-05-02 18:29 ` bugzilla-daemon
2025-05-02 18:30 ` bugzilla-daemon
2025-05-02 20:30 ` bugzilla-daemon
2025-05-02 21:53 ` bugzilla-daemon
2025-05-04 22:25 ` bugzilla-daemon
2025-05-05 16:09 ` bugzilla-daemon
2025-05-08 13:13 ` bugzilla-daemon [this message]
2026-03-21 10:39 ` bugzilla-daemon
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-220061-62941-JE4RGYOYPt@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.