linux-kernel - Re: regression: nested: L1 3.15+ fails to load kvm-intel on L0 <3.10

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 19 Mar 2015 21:08:17 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Stefan Bader <stefan.bader@...onical.com>, kvm@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ben Hutchings <ben@...adent.org.uk>
Subject: Re: regression: nested: L1 3.15+ fails to load kvm-intel on L0 <3.10



On 19/03/2015 20:58, Stefan Bader wrote:
> This was added in 3.10. So the range of kernels affected <3.10 back
> to when nested vmx became somewhat usable. For 3.2 Ben (and
> obviously us) would be affected. Apart from that, I believe, it is
> only 3.4 which has an active longterm. At least that change looks
> safer for stable as it sounds like correcting things and not adding
> a feature. I was able to cherry-pick that into a 3.2 kernel and
> then a 3.16 guest successfully can load the kvm-intel module again,
> of course with the same shortcomings as before.

Feel free to backport whatever you want to distro kernels.  But I'm
going to NACK for stable@ anything that is related to nested virt.

The code has changed so much that I simply cannot do a meaningful
review of most patches when applied to old codebases.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/