From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:53832 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751114AbeAYQfM (ORCPT ); Thu, 25 Jan 2018 11:35:12 -0500 Date: Thu, 25 Jan 2018 11:35:11 -0500 (EST) From: Paolo Bonzini To: Greg KH Cc: Liran Alon , Alexander Levin , konrad wilk , stable@vger.kernel.org, rkrcmar@redhat.com, linux-kernel@vger.kernel.org Message-ID: <1080098449.2581214.1516898111818.JavaMail.zimbra@redhat.com> In-Reply-To: <20180125095019.GB30255@kroah.com> References: <4693d8ab-1c86-44b6-b24f-009ee8766c1e@default> <20180125095019.GB30255@kroah.com> Subject: Re: [PATCH AUTOSEL for 4.14 006/100] KVM: nVMX/nSVM: Don't intercept #UD when running L2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: > > Just wanted stable maintainers to note that Jim, Paolo & myself decided > > eventually to revert this commit along with commit ae1f57670703 on > > upstream KVM. However, it is true that this commit makes commit > > ae1f57670703 more complete. Therefore we have 2 options here: > > 1) Apply this backport and sometime in the future also apply the reverts of > > both these commits with Paolo's commit which reverts them. > > Being "bug compatible" is good, I like that option :) It's not even a bug, just different behavior and in the end it turns out to be less surprising if we revert. So even better. :) > When is the revert patch going to hit Linus's tree? During the 4.16-rc1 > merge window? It's already there, commit ac9b305caa. But since this one was not marked for stable, ac9b305caa wasn't either. Paolo