netdev - Re: [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME un-configure ULP mode

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: <00b477c9-ef20-be95-1748-44efba18ebd3@intel.com>
Date:   Sun, 5 Apr 2020 09:46:26 +0300
From:   "Neftin, Sasha" <sasha.neftin@...el.com>
To:     Aaron Ma <aaron.ma@...onical.com>,
        Hans de Goede <hdegoede@...hat.com>,
        jeffrey.t.kirsher@...el.com, davem@...emloft.net,
        intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        "Lifshits, Vitaly" <vitaly.lifshits@...el.com>,
        "Neftin, Sasha" <sasha.neftin@...el.com>,
        "Tsai, Rex" <rex.tsai@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME
 un-configure ULP mode

On 4/3/2020 06:15, Aaron Ma wrote:
> Hi Jeffrey:
> 
> I have received the email that you apply this patch to next-queue branch
> dev-queue.
> 
> But after this branch is rebased to v5.6, I can't find it.
> 
> Will you apply again?
Aaron, Kai,
S0ix flow supported only on none ME system. Our PAE works to communicate 
this to OS vendors. You should get BIOS option to disable ME on your system.
This fix just will mask real problem on specific system - won't be solve 
the problem. I suggest recall this patch and Lenovo Carbon in DMI black 
list.
> 
> Thanks,
> Aaron
> 
> On 4/2/20 8:31 PM, Hans de Goede wrote:
>>
>> This fix fixes a real problem, on a popular model laptop
>> and since it just extends a timeout it is a pretty harmless
>> (no chance of regressions) fix. As such since there seems
>> to be no other solution in sight, can we please move forward
>> with this fix for now ?
Thanks,
Sasha