linux-kernel - Re: your recently submitted patch to fix BT RIP error shall be applied to 6.6 stable (I have a systematic crash on reboot in 6.6.23)

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: <1e37c6e5-7565-4564-8caf-3290cef6d134@free.fr>
Date: Wed, 27 Mar 2024 17:37:03 +0100
From: Eric Valette <eric.valette@...e.fr>
To: "Von Dentz, Luiz" <luiz.von.dentz@...el.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: your recently submitted patch to fix BT RIP error shall be
 applied to 6.6 stable (I have a systematic crash on reboot in 6.6.23)

On 27/03/2024 15:10, Eric Valette wrote:
> On 27/03/2024 15:01, Von Dentz, Luiz wrote:
>> Hi Eric,
>>
>> Then it must have been backported, which is kind of odd given that it 
>> was just merged for an -rc release that is still not consider stable, 
>> anyway the real culprit might actually be the following:
>>
>> https://patchwork.kernel.org/project/bluetooth/patch/20240327140855.896095-1-kiran.k@intel.com/
> 
> 
> Reading the patch, I'm afraid, if I apply the patch bt will then not 
> work if I reboot which is not what I want (I suspect  the firmware is 
> probably not unloaded when rebooting). Or am I making wrong assumptions?
> 
> NB: I may try to be sure...

Only get the first error and bt is still functional. Thanks.

Do not forget to queue the fix for stable.

-- eric