linux-kernel - Re: [PATCH 0/2] Fix resume failure due to PCID

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: <AE7FC1E9-017E-411A-87A3-83915A4ECBB9@amacapital.net>
Date:   Wed, 6 Sep 2017 21:15:55 -0700
From:   Andy Lutomirski <luto@...capital.net>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
        Borislav Petkov <bpetkov@...e.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] Fix resume failure due to PCID



> On Sep 6, 2017, at 8:25 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
>> On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski <luto@...nel.org> wrote:
>> Patch 1 is the fix.  Patch 2 is a comment that would have kept me from
>> chasing down a false lead.
> 
> Yes, this seems to fix things for me. Thanks.
> 
> Of course, right now that laptop has no working wifi with tip-of-tree
> due to some issues with the networking tree, but that's an independent
> thing and I could suspend and resume with this. So applied and pushed
> out,
> 
>                Linus


Great!

FWIW, there's still a possible glitch where doing EFI calls could corrupt ASID 0.  I figured that fixing that could wait for tomorrow.