linux-kernel - Re: [PATCH v2] x86/entry: Fix assumptions that the HW TSS is at the beginning of cpu

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: <20171126164338.fj7fd5r6ig5akdid@gmail.com>
Date:   Sun, 26 Nov 2017 17:43:38 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Andy Lutomirski <luto@...nel.org>
Cc:     Dave Hansen <dave.hansen@...el.com>, X86 ML <x86@...nel.org>,
        Borislav Petkov <bpetkov@...e.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Brian Gerst <brgerst@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2] x86/entry: Fix assumptions that the HW TSS is at the
 beginning of cpu_tss


* Andy Lutomirski <luto@...nel.org> wrote:

> On Sun, Nov 26, 2017 at 8:00 AM, Ingo Molnar <mingo@...nel.org> wrote:
> >
> > * Ingo Molnar <mingo@...nel.org> wrote:
> >
> >> Could you please do a delta to the very latest WIP.x86/mm instead?
> >>
> >> In the latest I have included the review tags already, and all the easy-to-do
> >> review feedback as well, so the delta should be rasonably small.
> >>
> >> These entry bits are destined for x86/urgent real soon, so Thomas and me are
> >> trying to pin the tree down and do delta changes only.
> >>
> >> If it's a simple full interdiff between your latest and WIP.x86/mm that's fine as
> >> well, can backmerge everything accordingly.
> >
> > Also feel free to include the two unwinder enhancements from you and Josh in the
> > delta series (as two separate patches) - WIP.x86/mm won't change more today.
> 
> I can do that.  Or if you want to get testing going, you can just pick
> them up -- I'm not planning on touching either one of of them.

I was hoping for proper changelogs and SOBs for both of them ;-)

Thanks,

	Ingo