linux-kernel - Re: [regression] ath11k broken in v6.7

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] [thread-next>] [day] [month] [year] [list]

Date: Mon, 22 Jan 2024 09:03:27 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Kalle Valo <kvalo@...nel.org>, ath11k@...ts.infradead.org
Cc: linux-wireless@...r.kernel.org, regressions@...ts.linux.dev,
 linux-kernel@...r.kernel.org
Subject: Re: [regression] ath11k broken in v6.7

On 22.01.24 08:36, Kalle Valo wrote:
> Kalle Valo <kvalo@...nel.org> writes:
>> Kalle Valo <kvalo@...nel.org> writes:
>>> Kalle Valo <kvalo@...nel.org> writes:
>>>
>>>> Just trying to make everyone aware because I suspect this will affect
>>>> quite a few people: ath11k is crashing during suspend on v6.7 due to a
>>>> mac80211 patch, more info:
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=218364

Many thx for the heads up, much appreciated. Sorry, forgot to add it to
the tracking myself: during the merge window thing are sometimes a bit
chaotic for myself as well. And I was head-down in rewriting some parts
of regzbot (see below).

>>>> Proposed fix:
>>>> https://patchwork.kernel.org/project/linux-wireless/patch/20240111170629.1257217-1-benjamin@sipsolutions.net/
>>>
>>> The fix is now applied:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/?id=556857aa1d0855aba02b1c63bc52b91ec63fc2cc
>>>
>>> I'll try to use regzbot for the first time, let's see how it goes:
>>>
>>> #regzbot introduced: 0a3d898ee9a8 ^
>>
>> Forgot to include the bug report:
>>
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218364

FWIW, that usage was slightly off and not how it's supposed to be done.
But whatever, let's ignore that. I'm reworking things currently
slightly, as you are not the first one that slightly got mislead -- and
the newer commands will hopefully be mire intuitive.

> #regzbot fix: 556857aa1d0855aba02b1c63bc52b91ec63fc2cc

Great, thx. Hope it reached mainline soon. Maybe once it's there you or
I should tell Greg to pick this up quickly for stable given that it
apparently "might affect quite a few people".

Thx again!

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.