Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751846AbeADA1J (ORCPT + 1 other); Wed, 3 Jan 2018 19:27:09 -0500 Received: from mail-pl0-f43.google.com ([209.85.160.43]:41062 "EHLO mail-pl0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751792AbeADA1H (ORCPT ); Wed, 3 Jan 2018 19:27:07 -0500 X-Google-Smtp-Source: ACJfBotanO2jI7YGEjK2USveuWaJA8Zepitw8GvW7hc7cp0YgN63640NQKD2bmzKFCJEk5/uBGA0/A== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs From: Andy Lutomirski X-Mailer: iPhone Mail (15C153) In-Reply-To: Date: Wed, 3 Jan 2018 16:27:04 -0800 Cc: Benjamin Gilbert , Ingo Molnar , Greg Kroah-Hartman , x86@kernel.org, LKML , linux-mm@kvack.org, stable@vger.kernel.org, Andy Lutomirski , Dave Hansen , Peter Zijlstra Content-Transfer-Encoding: 8BIT Message-Id: <69DD36C3-193E-4DCA-91A6-915BF3B434F7@amacapital.net> References: <20180103084600.GA31648@trogon.sfo.coreos.systems> <20180103092016.GA23772@kroah.com> <20180103154833.fhkbwonz6zhm26ax@gmail.com> <20180103223222.GA22901@trogon.sfo.coreos.systems> <20180103224902.GB22901@trogon.sfo.coreos.systems> To: Thomas Gleixner Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: > On Jan 3, 2018, at 2:58 PM, Thomas Gleixner wrote: > > > >> On Wed, 3 Jan 2018, Thomas Gleixner wrote: >> >>> On Wed, 3 Jan 2018, Benjamin Gilbert wrote: >>>> On Wed, Jan 03, 2018 at 11:34:46PM +0100, Thomas Gleixner wrote: >>>> Can you please send me your .config and a full dmesg ? >>> >>> I've attached a serial log from a local QEMU. I can rerun with a higher >>> loglevel if need be. >> >> Thanks! >> >> Cc'ing Andy who might have an idea and he's probably more away than I > > s/away/awake/ just to demonstrate the state I'm in ... > >> am. Will have a look tomorrow if Andy does not beat me to it. How much memory does the affected system have? It sounds like something is mapped in the LDT region and is getting corrupted because the LDT code expects to own that region. I got almost exactly this failure in an earlier version of the code when I typed the LDT base address macro. I'll try to reproduce. >> >> Thanks, >> >> tglx >>