Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp449492yba; Thu, 9 May 2019 00:04:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqzTR0ehgReFCiEDwIiDtUwtOl2kEEeUK9NCc5aiC6R657kX8leZPhaimYwqdxNgVRZOgq4P X-Received: by 2002:a63:1160:: with SMTP id 32mr3465154pgr.106.1557385481662; Thu, 09 May 2019 00:04:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557385481; cv=none; d=google.com; s=arc-20160816; b=qR8SefVTUoDFFkKNcb+XmhJ920Q1KcNE6NCvD6D901LrUGuZ/85lyl4j/9DUm8EKZu kKtuZrLlF2NqPuFN8dvgYcOW6XmsFukpw8HtPEJ8C24UIUIfslQO+3A/ntZ6S5SSY1BL HFux8BBlUET3b3R78WZiTuurLRkC8Ygpww+NZN8A1nArBpt2WAbdZi2K9dUGUefg1qs9 oMLsXw64lFczaTpPaxUw8KINoClWnzbpS95RbqPdlPty4f/HtT/3FcMVeCLTP7UyqoXL 0mPFfs4ph4BEDWwK48sGwHJU4KOXVKaTgrwv7k6yeCPflsFxbgYAvj3XBQ4zGNxCcWhH JuHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=PqrwUIm9JGDOb+G5bKrPs185rVUuCjYPX1/UUImiYTQ=; b=Nu29CdZMdp73zkeRQwizqgWeh7QCW2/DxaK7jhfVCaPZ1sz+TPjJCf7GCiwGOszcsP F2PywLDOYzL+26wd6JrkG9dv372iQmWoazS7sTxmiwInz0iO/GM98cTUkgHfAuCAnf7e ylWruYoZOD69M7oojv5XpoxqaO7qTBZ3xHOWcyaWgoTMz98klT9gxA/a2yHT60lAKvAp 80cLKT1BRPlJfxn4bPxbpOdrMWvw8020RVMlDp0mywpqJADm9T6pSdgm09irQIPTmiy+ rvrWgrPK8ZD9oTrSzAqNZ2n2YrWPE9obbOUWnaSR2OWrmP3eeVghvgI15kXmh5nPU1LX 576A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 33si1614153plv.293.2019.05.09.00.04.25; Thu, 09 May 2019 00:04:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726607AbfEIHDD (ORCPT + 99 others); Thu, 9 May 2019 03:03:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51430 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725908AbfEIHDD (ORCPT ); Thu, 9 May 2019 03:03:03 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 15737C05E767; Thu, 9 May 2019 07:03:03 +0000 (UTC) Received: from localhost (ovpn-12-17.pek2.redhat.com [10.72.12.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3417419C77; Thu, 9 May 2019 07:02:59 +0000 (UTC) Date: Thu, 9 May 2019 15:02:57 +0800 From: Baoquan He To: linux-kernel@vger.kernel.org Cc: tglx@linutronix.de, mingo@kernel.org, bp@alien8.de, hpa@zytor.com, kirill.shutemov@linux.intel.com, x86@kernel.org, dyoung@redhat.com Subject: [PATCH v5 2/3] x86/kexec/64: Error out if try to jump to old 4-level kernel from 5-level kernel Message-ID: <20190509070257.GF24922@MiWiFi-R3L-srv> References: <20190509013644.1246-1-bhe@redhat.com> <20190509013644.1246-3-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190509013644.1246-3-bhe@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Thu, 09 May 2019 07:03:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If the running kernel has 5-level paging activated, the 5-level paging mode is preserved across kexec. If the kexec'ed kernel does not contain support for handling active 5-level paging mode in the decompressor, the decompressor will crash with #GP. Prevent this situation at load time. If 5-level paging is active, check the xloadflags whether the kexec kernel can handle 5-level paging at least in the decompressor. If not, reject the load attempt and print out error message. Signed-off-by: Baoquan He Acked-by: Kirill A. Shutemov --- v4->v5: Update the output error message per tglx's comment. arch/x86/kernel/kexec-bzimage64.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/x86/kernel/kexec-bzimage64.c b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..7f439739ea3d 100644 --- a/arch/x86/kernel/kexec-bzimage64.c +++ b/arch/x86/kernel/kexec-bzimage64.c @@ -321,6 +321,11 @@ static int bzImage64_probe(const char *buf, unsigned long len) return ret; } + if (!(header->xloadflags & XLF_5LEVEL) && pgtable_l5_enabled()) { + pr_err("bzImage cannot handle 5-level paging mode.\n"); + return ret; + } + /* I've got a bzImage */ pr_debug("It's a relocatable bzImage64\n"); ret = 0; -- 2.17.2