linux-kernel - Re: [PATCH urgent 0/3] __restore_processor

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: <20171215113127.uga2keiidjgs7quk@gmail.com>
Date:   Fri, 15 Dec 2017 12:31:27 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        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>,
        Pavel Machek <pavel@....cz>, Zhang Rui <rui.zhang@...el.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [PATCH urgent 0/3] __restore_processor_state() fixes


* Jarkko Nikula <jarkko.nikula@...ux.intel.com> wrote:

> On 12/15/2017 03:28 AM, Rafael J. Wysocki wrote:
> > On Thursday, December 14, 2017 10:19:04 PM CET Andy Lutomirski wrote:
> > > __restore_processor_state() was spaghetti code, made no sense, and
> > > had bugs.  And I broke resume on 32-bit systems.  This series cleans
> > > it up and fixes it (hopefully!).
> > > 
> > > Andy Lutomirski (3):
> > >    x86/power/64: Use struct desc_ptr for the IDT in struct saved_context
> > >    x86/power/32: Move SYSENTER MSR restoration to fix_processor_context()
> > >    x86/power: Make restore_processor_context() sane
> > 
> > For all three:
> > 
> > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > 
>
> Works still after split up so my tested by remains. Please note Pavel gave
> his reported/tested-by in 3/3.

Thanks, I've updated all the changelogs - and I've also added your Reported-by tag 
to patch #3.

Thanks,

	Ingo