From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f69.google.com (mail-pg0-f69.google.com [74.125.83.69]) by kanga.kvack.org (Postfix) with ESMTP id 8E9216B04A2 for ; Wed, 3 Jan 2018 19:27:08 -0500 (EST) Received: by mail-pg0-f69.google.com with SMTP id x10so47645pgx.12 for ; Wed, 03 Jan 2018 16:27:08 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id 34sor692992plz.16.2018.01.03.16.27.07 for (Google Transport Security); Wed, 03 Jan 2018 16:27:07 -0800 (PST) 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 In-Reply-To: Date: Wed, 3 Jan 2018 16:27:04 -0800 Content-Transfer-Encoding: quoted-printable 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> Sender: owner-linux-mm@kvack.org List-ID: To: Thomas Gleixner 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 > On Jan 3, 2018, at 2:58 PM, Thomas Gleixner wrote: >=20 >=20 >=20 >> On Wed, 3 Jan 2018, Thomas Gleixner wrote: >>=20 >>> 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 ? >>>=20 >>> I've attached a serial log from a local QEMU. I can rerun with a higher= >>> loglevel if need be. >>=20 >> Thanks! >>=20 >> Cc'ing Andy who might have an idea and he's probably more away than I >=20 > s/away/awake/ just to demonstrate the state I'm in ... >=20 >> 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 m= apped in the LDT region and is getting corrupted because the LDT code expect= s to own that region. I got almost exactly this failure in an earlier version of the code when I t= yped the LDT base address macro. I'll try to reproduce. >>=20 >> Thanks, >>=20 >> tglx >>=20 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org