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, 4 Dec 2023 09:12:39 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Johannes Berg <johannes@...solutions.net>
Cc:     Eliad Peller <eliad@...ery.com>,
        "John W. Linville" <linville@...driver.com>,
        Gregory Greenman <gregory.greenman@...el.com>,
        Linus Lotz <register+kernelbugzilla@...z.li>,
        Darrell Enns <darrell@...rellenns.com>,
        Bagas Sanjaya <bagasdotme@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Wireless <linux-wireless@...r.kernel.org>
Subject: Re: Fwd: iwlwifi: rfkill locking up kernel 6.5.12, 6.6.2

On 02.12.23 07:07, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 30.11.23 09:23, Bagas Sanjaya wrote:
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>
>>> Rfkilling the iwlwifi can lock up my machine, rfkill will not
>>> respond and other networking related things (e.g. ip a or ip r) I
>>> see this on 6.5.12 and 6.6.2 (fedora kernel). On 6.5.11 it does not
>>> lockup AFAICT, but also shows kernel oops. WiFi Hardware: AC 8265
>>
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218206
> 
> TWIMC: More people that seem to be affected by the same problem joined
> the report. And one user performed a bisection on 6.6.y. According to
> that the problem is caused by a 6.6.y-backport of 37fb29bd1f90f1 ("wifi:
> iwlwifi: pcie: synchronize IRQs before NAPI") [v6.7-rc1] from Johannes.
> 
> Another reported user also stated that the same problem happens on
> 6.7-rc3 as well. No confirmation yet that 37fb29bd1f90f1 causes it
> there, but it seems likely.

TWIMC, it was now confirmed that reverting 37fb29bd1f90f1 in 6.7-rc
fixes the problem.

The bugzilla ticket has the details; it's sadly all a bit mess (it was
afaics actually a gentoo user that confirmed the above in a downstream
bug tracker [https://bugs.gentoo.org/918128#c21] and a gentoo kernel dev
forwarded the result to our bugzilla...).

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ