linux-kernel - Re: [regression] iwlwifi driver broken on Intel 3165 network card

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]

Message-ID: <c71e376e-4e44-a1b3-6feb-2ed1ba7d325b@leemhuis.info>
Date:   Wed, 12 Jul 2023 11:59:25 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Johannes Berg <johannes@...solutions.net>,
        Linux regressions mailing list <regressions@...ts.linux.dev>,
        Aloka Dixit <quic_alokad@...cinc.com>,
        John Crispin <john@...ozen.org>
Cc:     Aditya Kumar Singh <quic_adisi@...cinc.com>,
        linux-wireless@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [regression] iwlwifi driver broken on Intel 3165 network card

On 10.07.23 17:02, Johannes Berg wrote:
> On Mon, 2023-07-10 at 10:32 +0200, Linux regression tracking (Thorsten
> Leemhuis) wrote:
>> Hi, Thorsten here, the Linux kernel's regression tracker.
>>
>> I noticed a regression report in bugzilla.kernel.org. As many (most?)
>> kernel developers don't keep an eye on it, I decided to forward it by mail.
>>
>> Aloka Dixit, apparently it's cause by a change of yours: bd54f3c2907
>> ("wifi: mac80211: generate EMA beacons in AP mode") [v6.4-rc1]
>>
> 
> That bisect result seems unlikely to be correct. Those changes are in
> "how to get beacons" (in AP mode) which isn't even used in client mode
> here.

You where right, the second bisect resulted in a different outcome.
Currently looks like 5fc3f6c90cc ("r8169: consolidate disabling ASPM
before EPHY access") [v6.4-rc1] is the culprit; this is somewhat odd as
well, but confirmed partially, as blacklisting r8169 apparently fixes
the issue. I nevertheless asked the reporter to recheck by reverting
that commit. Once that happened I'll notify the author of 5fc3f6c90cc.

Thx again and sorry for the noise.

BTW, in case anyone wants details, see:
https://bugzilla.kernel.org/show_bug.cgi?id=217635

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.