linux-kernel - Re: [PATCH] Bluetooth: Apply initial command workaround for more Intel chips

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <343accce-e361-3154-409d-78ecc2736024@leemhuis.info>
Date:   Thu, 20 Jan 2022 16:13:29 +0100
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Marcel Holtmann <marcel@...tmann.org>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>, Takashi Iwai <tiwai@...e.de>,
        Fernando Ramos <greenfoo@....eu>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Luiz Augusto von Dentz <luiz.dentz@...il.com>,
        Tedd Ho-Jeong An <tedd.an@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-bluetooth@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: Apply initial command workaround for more
 Intel chips

On 20.01.22 16:07, Marcel Holtmann wrote:
> 
>> Could the bluetooth maintainers please provide a status update? I wonder
>> if it's time to bring this regression to Linus attention, as it seems to
>> be an issue that hits quite a few users -- and at the same takes quite a
>> long time to get fixed for a issue where a patch with a workaround was
>> already proposed one and a half months ago.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b

Ahh, okay, many thx for the update, it wasn't clear enough to me that
this should fix the issue. Would have been nice if the commit would have
had "Link:" tags to all reports about the issue (as explained in
Documentation/process/submitting-patches.rst and
Documentation/process/5.Posting.rst ), as that would have avoided confusion.

Anyway, to close this:

#regzbot introduced: ffcba827c0a1d
#regzbot fixed-by: 95655456e7cee858a23793f67025765b4c4c227b

Ciao, Thorsten