linux-kernel - Re: [GIT PULL] KVM changes for Linux 4.19-rc5

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]

Date:   Fri, 21 Sep 2018 18:25:45 +0200
From:   Greg KH <gregkh@...ux-foundation.org>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     linux-kernel@...r.kernel.org, rkrcmar@...hat.com,
        kvm@...r.kernel.org
Subject: Re: [GIT PULL] KVM changes for Linux 4.19-rc5

On Fri, Sep 21, 2018 at 04:06:06PM +0200, Paolo Bonzini wrote:
> Greg,
> 
> The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:
> 
>   Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> for you to fetch changes up to 26b471c7e2f7befd0f59c35b257749ca57e0ed70:
> 
>   KVM: nVMX: Fix bad cleanup on error of get/set nested state IOCTLs (2018-09-20 18:54:08 +0200)
> 
> ----------------------------------------------------------------
> This pull request is slightly bigger than usual at this stage, but
> I swear I would have sent it the same to Linus!  The main cause for
> this is that I was on vacation until two weeks ago and it took a while
> to sort all the pending patches between 4.19 and 4.20, test them and
> so on.
> 
> It's mostly small bugfixes and cleanups, mostly around x86 nested
> virtualization.  One important change, not related to nested
> virtualization, is that the ability for the guest kernel to trap CPUID
> instructions (in Linux that's the ARCH_SET_CPUID arch_prctl) is now
> masked by default.  This is because the feature is detected through an
> MSR; a very bad idea that Intel seems to like more and more.  Some
> applications choke if the other fields of that MSR are not initialized
> as on real hardware, hence we have to disable the whole MSR by default,
> as was the case before Linux 4.12.

Now pulled, thanks.

greg k-h