[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201106003932.GQ25636@zn.tnic>
Date: Fri, 6 Nov 2020 01:39:32 +0100
From: Borislav Petkov <bp@...en8.de>
To: Michael Roth <michael.roth@....com>
Cc: Joerg Roedel <joro@...tes.org>, x86@...nel.org,
Juergen Gross <jgross@...e.com>,
Tom Lendacky <thomas.lendacky@....com>,
Joerg Roedel <jroedel@...e.de>,
Mike Stunes <mstunes@...are.com>,
Kees Cook <keescook@...omium.org>, kvm@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Cfir Cohen <cfir@...gle.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
linux-kernel@...r.kernel.org,
Sean Christopherson <sean.j.christopherson@...el.com>,
virtualization@...ts.linux-foundation.org,
Martin Radev <martin.b.radev@...il.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Andy Lutomirski <luto@...nel.org>, hpa@...or.com,
Erdem Aktas <erdemaktas@...gle.com>,
David Rientjes <rientjes@...gle.com>,
Dan Williams <dan.j.williams@...el.com>,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH v7 01/72] KVM: SVM: nested: Don't allocate VMCB
structures on stack
On Thu, Nov 05, 2020 at 06:31:53PM -0600, Michael Roth wrote:
> I can confirm that patch fixes the issue. It is indeed a 5.9.1 tree, but
> looks like the SEV-ES patches didn't go in until v5.10-rc1
Yes, they went into 5.10-rc1 during the merge window.
> (this tree had a backport of them), so stable trees shouldn't be
> affected.
Ah, ok, that makes sense.
Thanks for checking!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists