Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753297AbbGYE6s (ORCPT ); Sat, 25 Jul 2015 00:58:48 -0400 Received: from mail-la0-f48.google.com ([209.85.215.48]:35122 "EHLO mail-la0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001AbbGYE6q (ORCPT ); Sat, 25 Jul 2015 00:58:46 -0400 MIME-Version: 1.0 In-Reply-To: <55B30CE3.2010902@oracle.com> References: <049fdbab8ae2ecac1c8b40ecd558e9df45ccd5d3.1437592883.git.luto@kernel.org> <55B01745.4010702@oracle.com> <55B30CE3.2010902@oracle.com> From: Andy Lutomirski Date: Fri, 24 Jul 2015 21:58:23 -0700 Message-ID: Subject: Re: [PATCH v3 1/3] x86/ldt: Make modify_ldt synchronous To: Boris Ostrovsky Cc: Andy Lutomirski , Peter Zijlstra , Steven Rostedt , "security@kernel.org" , X86 ML , Borislav Petkov , Sasha Levin , "linux-kernel@vger.kernel.org" , Konrad Rzeszutek Wilk , Andrew Cooper , Jan Beulich , xen-devel , stable Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1750 Lines: 51 On Fri, Jul 24, 2015 at 9:13 PM, Boris Ostrovsky wrote: > > > On 07/22/2015 06:20 PM, Boris Ostrovsky wrote: >> >> On 07/22/2015 03:23 PM, Andy Lutomirski wrote: >>> >>> >>> + error = -ENOMEM; >>> + new_ldt = alloc_ldt_struct(newsize); >>> + if (!new_ldt) >>> goto out_unlock; >>> - } >>> - fill_ldt(&ldt, &ldt_info); >>> - if (oldmode) >>> - ldt.avl = 0; >>> + if (old_ldt) { >>> + memcpy(new_ldt->entries, old_ldt->entries, >>> + oldsize * LDT_ENTRY_SIZE); >>> + } >>> + memset(new_ldt->entries + oldsize * LDT_ENTRY_SIZE, 0, >>> + (newsize - oldsize) * LDT_ENTRY_SIZE); >> >> >> We need to zero out full page (probably better in alloc_ldt_struct() with >> vmzalloc/__GFP_ZERO) --- Xen checks whole page that is assigned to G/LDT >> and gets unhappy if an invalid descriptor is found there. >> >> This fixes one problem. There is something else that Xen gets upset about, >> I haven't figured what it is yet (and I am out tomorrow so it may need to >> wait until Friday). >> > > > What I thought was another problem turned out not to be one so both 64- and > 32-bit tests passed on 64-bit PV (when allocated LDT is zeroed out) > > However, on 32-bit kernel the test is failing multicpu test, I don't know > yet what it is. Test case bug or unrelated kernel bug depending on your point of view. I forgot that x86_32 and x86_64 have very different handling of IRET faults. Wait for v2 :) --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/