linux-kernel - Re: linux-next: manual merge of the kvm tree with Linus' and the tip trees

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]

Date:   Tue, 16 Jan 2018 01:55:08 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Radim Krčmář <rkrcmar@...hat.com>,
        KVM <kvm@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        David Woodhouse <dwmw@...zon.co.uk>,
        Tom Lendacky <thomas.lendacky@....com>,
        Brijesh Singh <brijesh.singh@....com>,
        Borislav Petkov <bp@...en8.de>
Subject: Re: linux-next: manual merge of the kvm tree with Linus' and the tip
 trees


* Paolo Bonzini <pbonzini@...hat.com> wrote:

> On 15/01/2018 19:36, Thomas Gleixner wrote:
> >> Can KVM folks please stop doing random changes to the cpufeatures code
> >> without talking to x86 maintainers and Borislav?
> >>
> >> This wants to go through TIP or at least reviewed and acked.
> > In fact it needs to go through TIP. We spent a lot of effort to make the
> > backporting of all this mess simple and this is just shooting a hole in it.
> 
> I do understand why you want this to go through TIP, but I'm not sure
> why a change to Processor Tracing is related to PTI or retpolines.  I'm
> also not sure why it is a problem for backportability, since we always
> try to send pull requests after TIP.  Is it because 7*32+15 will be free
> in 4.16 but not earlier?

It is because certain central x86 changes (such as changes to processor flags)
are kept on a v4.14 base to keep the PTI backporting efforts manageable.

Please revert (or rebase) this change from the KVM tree, and submit it separately, 
as it should have been done to begin with. Please also follow this process in the 
future: all x86 changes outside arch/x86/kvm/ need an explicit ack from an x86 
maintainer.

Thanks,

	Ingo