From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Marcel Holtmann <marcel@holtmann.org>,
Vasily Khoruzhick <anarsoul@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "Bluetooth: Align minimum encryption key size for LE and BR/EDR connections"
Date: Wed, 12 Jun 2019 13:04:57 +0300 [thread overview]
Message-ID: <77E07614-6F68-4661-BC6D-2BD610DBD62A@gmail.com> (raw)
In-Reply-To: <9ad95905975e09646f0f2aa967140881cbbe3477.camel@hadess.net>
Hi,
On 12 Jun 2019, at 12.38, Bastien Nocera <hadess@hadess.net> wrote:
>
> On Wed, 2019-06-12 at 09:07 +0200, Greg Kroah-Hartman wrote:
>> On Tue, Jun 11, 2019 at 11:36:26PM +0200, Marcel Holtmann wrote:
>>> Hi Vasily,
>>>
>>>> Can we get this revert merged into stable branches? Bluetooth HID
>>>> has
>>>> been broken for many devices for quite a while now and RFC patch
>>>> that
>>>> fixes the breakage hasn't seen any movement for almost a month.
>>>
>>> lets send the RFC patch upstream since it got enough feedback that
>>> it fixes the issue.
>>
>> According to Hans, the workaround did not work.
>
> Is it possible that those folks were running Fedora, and using a
> version of bluetoothd without a fix for using dbus-broker as the D-Bus
> daemon implementation?
>
> I backported the fix in an update last week:
> https://bugzilla.redhat.com/show_bug.cgi?id=1711594
I don’t know if that’s the case, but at least based on the comment here:
https://bugzilla.kernel.org/show_bug.cgi?id=203643#c10
it looks like there’s still a race with controllers that do support reading the encryption key size. The peer device may send an L2CAP Connect Request before we’ve completed reading the key size, in which case we’d still reject the request. For making this work again I’m not aware of any other quick solution than a revert.
Johan
next prev parent reply other threads:[~2019-06-12 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 5:20 [PATCH] Revert "Bluetooth: Align minimum encryption key size for LE and BR/EDR connections" Vasily Khoruzhick
2019-05-22 6:38 ` Marcel Holtmann
2019-05-22 7:08 ` Marcel Holtmann
2019-05-23 14:52 ` Vasily Khoruzhick
2019-06-11 19:56 ` Vasily Khoruzhick
2019-06-11 21:36 ` Marcel Holtmann
2019-06-12 7:07 ` Greg Kroah-Hartman
2019-06-12 9:38 ` Bastien Nocera
2019-06-12 10:04 ` Johan Hedberg [this message]
2019-06-13 7:35 ` Greg Kroah-Hartman
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=77E07614-6F68-4661-BC6D-2BD610DBD62A@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=anarsoul@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).