From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B752C43387 for ; Fri, 11 Jan 2019 08:46:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DBE282084C for ; Fri, 11 Jan 2019 08:46:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="VJ44E+RB"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="FRacTxA9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729462AbfAKIqK (ORCPT ); Fri, 11 Jan 2019 03:46:10 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:34313 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725813AbfAKIqJ (ORCPT ); Fri, 11 Jan 2019 03:46:09 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 98CF820F50; Fri, 11 Jan 2019 03:46:06 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 11 Jan 2019 03:46:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=qo9RxF0MPjB5AAu/jjul280pUEY jxgw9tGGz3a+rZ0s=; b=VJ44E+RBsJ2AEMFSlwjiL4iZgMjpfpsyuplAw5TfKhF W483FhhBfpAINjodDNUg232055Tx/fxEYLJ7TrVKfLc/aVSo2qY4+BYi9TEOZAkp KyvxZ7+yxt0fPdLFkW6awEsMX4QPQjdHtV8uudc2kEVPtKTWqTMIbM8JrRloOhWT fSOl1enRwyFWCRA318XWz/oPJnL10NtySLb2fmjDBbodV8/ZWIVH6ss4nPA5kUdI DMT8XVsAWN/fyQOzfrDFrMAe1X9x7F0yp0jvbpSVyz3ZjufJh2GdJTXDwEF3QRsg 94WXf1AkjONn0eOOeBnnaZEle1g0cuTGuz4U9c/Ovfw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=qo9RxF 0MPjB5AAu/jjul280pUEYjxgw9tGGz3a+rZ0s=; b=FRacTxA9sfiTke7dXBES6e znAMM+Ap3L/Uxv6hVnQfNyV3KO/+9o3y/HinysfFxsO/0QcPySqz6nQDodiK4AmP kNDZkWMwPvkAz00nXQkFQd+sLFPfAs8YlaDTo7tPT4wJkjxYsz0RpqknCPGqPrWm Otw/eecbor/Q+vTrXX5wy2p1njef1W9ok4/TgVl0AwrSxdY5DlQPlRaSpt9VY5xo bAw+eS3V4F4rCEeSQZB3kBLX4CZ4Xsfjj6g1KkwqAYKcRuqjIzsfZ5ZhiSzTtbGd +iLOOorzMMI7d2lfI8/5/TtTDXB1UwPWM5yudCwxvbXskJS2+UEZpm41Y/89h+Lg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfeeggdduvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfh ggtggujggfsehttdertddtredvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehk rhhorghhrdgtohhmqeenucffohhmrghinhepkhgvrhhnvghlrdhorhhgpdguvggsihgrnh drohhrghenucfkphepudejkedrvddvkedrfeeirdduudeinecurfgrrhgrmhepmhgrihhl fhhrohhmpehgrhgvgheskhhrohgrhhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (unknown [178.228.36.116]) by mail.messagingengine.com (Postfix) with ESMTPA id 6DD24100E4; Fri, 11 Jan 2019 03:46:05 -0500 (EST) Date: Fri, 11 Jan 2019 09:46:03 +0100 From: Greg KH To: Juergen Gross Cc: Hans van Kranenburg , xen-devel@lists.xenproject.org, stable , "Kirill A. Shutemov" Subject: Re: [Xen-devel] Linux 4.19.5 fails to boot as Xen dom0 Message-ID: <20190111084603.GC13446@kroah.com> References: <8faec76b-ab44-3148-165d-0f3c9f497de2@suse.com> <20181129132657.nlzxzqfdvngjsfvk@black.fi.intel.com> <20181206111352.GQ19891@kroah.com> <20181206114609.GA19522@kroah.com> <26a64020-3974-ec4d-f64d-65669e87d505@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Jan 11, 2019 at 08:59:52AM +0100, Juergen Gross wrote: > On 22/12/2018 12:14, Juergen Gross wrote: > > On 06/12/2018 12:46, Greg KH wrote: > >> On Thu, Dec 06, 2018 at 12:31:15PM +0100, Juergen Gross wrote: > >>> On 06/12/2018 12:13, Greg KH wrote: > >>>> On Thu, Nov 29, 2018 at 02:35:17PM +0100, Juergen Gross wrote: > >>>>> On 29/11/2018 14:26, Kirill A. Shutemov wrote: > >>>>>> On Thu, Nov 29, 2018 at 09:41:25AM +0000, Juergen Gross wrote: > >>>>>>> On 29/11/2018 02:22, Hans van Kranenburg wrote: > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> As also seen at: > >>>>>>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914951 > >>>>>>>> > >>>>>>>> Attached there are two serial console output logs. One is starting with > >>>>>>>> Xen 4.11 (from debian unstable) as dom0, and the other one without Xen. > >>>>>>>> > >>>>>>>> [ 2.085543] BUG: unable to handle kernel paging request at > >>>>>>>> ffff888d9fffc000 > >>>>>>>> [ 2.085610] PGD 200c067 P4D 200c067 PUD 0 > >>>>>>>> [ 2.085674] Oops: 0000 [#1] SMP NOPTI > >>>>>>>> [ 2.085736] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > >>>>>>>> 4.19.0-trunk-amd64 #1 Debian 4.19.5-1~exp1+pvh1 > >>>>>>>> [ 2.085823] Hardware name: HP ProLiant DL360 G7, BIOS P68 05/21/2018 > >>>>>>>> [ 2.085895] RIP: e030:ptdump_walk_pgd_level_core+0x1fd/0x490 > >>>>>>>> [...] > >>>>>>> > >>>>>>> The offending stable commit is 4074ca7d8a1832921c865d250bbd08f3441b3657 > >>>>>>> ("x86/mm: Move LDT remap out of KASLR region on 5-level paging"), this > >>>>>>> is commit d52888aa2753e3063a9d3a0c9f72f94aa9809c15 upstream. > >>>>>>> > >>>>>>> Current upstream kernel is booting fine under Xen, so in general the > >>>>>>> patch should be fine. Using an upstream kernel built from above commit > >>>>>>> (with the then needed Xen fixup patch 1457d8cf7664f34c4ba534) is fine, > >>>>>>> too. > >>>>>>> > >>>>>>> Kirill, are you aware of any prerequisite patch from 4.20 which could be > >>>>>>> missing in 4.19.5? > >>>>>> > >>>>>> I'm not. > >>>>>> > >>>>>> Let me look into this. > >>>>>> > >>>>> > >>>>> What is making me suspicious is the failure happening just after > >>>>> releasing the init memory. Maybe there is an access to .init.data > >>>>> segment or similar? The native kernel booting could be related to the > >>>>> usage of 2M mappings not being available in a PV-domain. > >>>> > >>>> Did this ever get fixed anywhere that I can properly backport it to the > >>>> 4.19.y tree? > >>> > >>> https://lore.kernel.org/lkml/20181130202328.65359-2-kirill.shutemov@linux.intel.com/ > >>> > >>> Still pending upstream. Just pinged tglx. > >> > >> Thanks, it should have gotten a cc: stable@ tag, but I can watch out for > >> it... > > > > It's upstream now: commit 16877a5570e0c5f4270d5b17f9bab427bcae9514 > > Any reason you didn't include this patch in 4.19.14? I was catching up on pending patches and got to this yesterday. It should now be queued up already for the next releases, right? thanks, greg k-h