linux-kernel - Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2

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 for Android: free password hash cracker in your pocket

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

Message-ID: <13aea525-108a-e018-987d-2447ff1d42df@leemhuis.info>
Date:   Fri, 14 Apr 2023 14:48:31 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Jianmin Lv <lvjianmin@...ngson.cn>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>,
        Huacai Chen <chenhuacai@...ngson.cn>,
        Bob Moore <robert.moore@...el.com>,
        acpica-devel@...ts.linuxfoundation.org,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Huacai Chen <chenhuacai@...nel.org>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since
 6.2

On 19.03.23 08:20, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 22.02.23 08:57, Thorsten Leemhuis wrote:
>>
>> I noticed a regression report in bugzilla.kernel.org. As many (most?)
>> kernel developer don't keep an eye on it, I decided to forward it by
>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217069 :
> 
> An issue that looked like a network bug was now bisected and it turns
> out it's cause by 5c62d5aab875 ("ACPICA: Events: Support fixed PCIe wake
> event") which Huacai Chen provided. Could you take a look at the ticket
> linked above?

Jianmin did get close to a proper fix a while ago
(https://bugzilla.kernel.org/show_bug.cgi?id=217069#c46 ), but it
appears there wasn't any progress to fix this during the last week. Or
did I miss it?

This is kinda unsatisfying, as the culprit is now known for nearly four
weeks; especially as this is a issue that is present in 6.2 since it was
released and would have been possible to fix there and in mainline with
a simple revert. We even got close to one two weeks ago already
(https://bugzilla.kernel.org/show_bug.cgi?id=217069#c49 ).

#sigh

I'd say we should revert this. Rafael, what's your opinion here?

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.

#regzbot poke