From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754871AbbG3RIf (ORCPT ); Thu, 30 Jul 2015 13:08:35 -0400 Received: from smtp.citrix.com ([66.165.176.89]:65263 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753544AbbG3RId (ORCPT ); Thu, 30 Jul 2015 13:08:33 -0400 X-IronPort-AV: E=Sophos;i="5.15,577,1432598400"; d="scan'208";a="286208772" Message-ID: <55BA59B1.5000600@citrix.com> Date: Thu, 30 Jul 2015 18:06:57 +0100 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Boris Ostrovsky , Borislav Petkov CC: "security@kernel.org" , Jan Beulich , Peter Zijlstra , X86 ML , , Steven Rostedt , xen-devel , Andy Lutomirski , Sasha Levin Subject: Re: [Xen-devel] [PATCH v5 0/4] x86: modify_ldt improvement, test, and config option References: <55BA487E.9030708@oracle.com> <20150730160555.GB28617@nazgul.tnic> <55BA4D08.9070306@citrix.com> <55BA5173.401@oracle.com> In-Reply-To: <55BA5173.401@oracle.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30/07/15 17:31, Boris Ostrovsky wrote: > On 07/30/2015 12:12 PM, Andrew Cooper wrote: >> On 30/07/15 17:05, Borislav Petkov wrote: >>> On Thu, Jul 30, 2015 at 11:53:34AM -0400, Boris Ostrovsky wrote: >>>> As far as Xen guests are concerned, >>>> >>>> Tested-by: Boris Ostrovsky >>> Does that mean, this patch 1/4 fixes the 32bit issue you guys are still >>> debugging on the v4 thread? Or does that need more fixing? >>> >> I was going to say... This v5 pre-dates figuring out what was wrong with >> 32bit Xen. v5 1/4 is still susceptible. >> >> Boris: does your Tested-by cover v5 + proposed fix? >> > > Only V5, no extra changes. Including running the ldt_gdt test? > > And perhaps dropping aliases in xen_alloc_ldt() may be sufficient > since with that done we will only have one mapping so a subsequent > fault will have "correct" cr2 provided by the hypervisor (from your > earlier email it sounded that hypervisor may have been providing > incorrect cr2 if alias exists) They are sufficient to fix the first of the two bugs, but the free side still has no protection against a missing l2, unless I am missing something in the rest of the series? ~Andrew