Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp1299145ybg; Wed, 23 Oct 2019 13:31:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqxE3g4PaqRHMGYR/8a7KlYicISjMqi4+O8lCYuog9+As8xOHkYFQTUrGKnBjVFjWxHiWIb+ X-Received: by 2002:a05:6402:7d2:: with SMTP id u18mr40443321edy.23.1571862695636; Wed, 23 Oct 2019 13:31:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571862695; cv=none; d=google.com; s=arc-20160816; b=uzJ+UD7eIIDswJ67IT2PfEvdNx+ZRN+Q/3lblmEAsrsdGYZjVQ6GnvC3awABPqUgYE t6UusnNG1UIa1e/kf6uTHZyY+gL8FWc0K16F2N0LgQHpt+OoctRwLpc++/0ZLdWyD8e2 q1zsOjBvGmSK6H755vlelb9HJvL5mvvpsDbM9+eoUqZkpbPPkQZxro5+YMWYRQpsXpN1 zpdJst2nQCg2/v3yK/GcSIz5pmGMTb4Bs+8/3iB8qSxgT5kPlh5UgYjl9qrM4XEFxmdK 7gtlPVmXt/AVqtbBULoPywgOIdFRYcm004Lpq+rsNGIhLgskc2cWe4FmeskoLWt46heH LPZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature; bh=dNn6WpAdg6wu4jO8r4Tldu5kvsjSDr3B6R6TofrCToQ=; b=jMprw20geDTD9S1uoaxLzPf65wn3Y3yXieE4HU0W9GIw0NHwpf6otyFNH5+XIEpn/E jNuyxUo21THfAquDha2pTkDWtso59loni8q2n8UKwvlJX4AGaAuO41rognQv+6JXpY+o Mheiigqr4Osiy4hrYjSvHOQZNpblRNyCJrpyNN7M9+g4D64bmfPBpT70qG2e2OAw1I1H yFZ/FDQr4T9MvFxzkpOYqfjYwLnzCGsr6NbTTr1jD6yH6cJ8A13UPeXL806Jm71r9LEP cXlJnS6Mgi7TjSF6I3Gogs3qZcHebIjAsFElJ/GOTs+JhZ9j1R2sod6uo0niHQ/mM9U7 z6Qg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Ev/oVl5b"; 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=pass (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 v18si12737655ejd.115.2019.10.23.13.31.10; Wed, 23 Oct 2019 13:31:35 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Ev/oVl5b"; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406365AbfJWOTy (ORCPT + 99 others); Wed, 23 Oct 2019 10:19:54 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:22468 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2406348AbfJWOTx (ORCPT ); Wed, 23 Oct 2019 10:19:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571840392; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dNn6WpAdg6wu4jO8r4Tldu5kvsjSDr3B6R6TofrCToQ=; b=Ev/oVl5b+TFEihxRo6NjCIwLtzqWjgzCkhg6VtB1PY7jPSqx8WlRMuq0TWTYU9ks+AKhfi fNDJrxGwQ9SmHPk8E8yr8Ev8vJyEhyanvtHKNU+qOGNzUkMiMxSXThIIktfFXmfMtE9osx x82M+pXUzAVV97Lwp0pC4nc//rzVdD4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-383-ZuOZjN2XOXe4_UlW_M-Jbw-1; Wed, 23 Oct 2019 10:19:49 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 44B171005500; Wed, 23 Oct 2019 14:19:48 +0000 (UTC) Received: from localhost.localdomain.com (ovpn-12-33.pek2.redhat.com [10.72.12.33]) by smtp.corp.redhat.com (Postfix) with ESMTP id 43B725C1D4; Wed, 23 Oct 2019 14:19:36 +0000 (UTC) From: Lianbo Jiang To: linux-kernel@vger.kernel.org Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org, bhe@redhat.com, dyoung@redhat.com, jgross@suse.com, dhowells@redhat.com, Thomas.Lendacky@amd.com, ebiederm@xmission.com, vgoyal@redhat.com, kexec@lists.infradead.org Subject: [PATCH 1/2 v5] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified Date: Wed, 23 Oct 2019 22:19:11 +0800 Message-Id: <20191023141912.29110-2-lijiang@redhat.com> In-Reply-To: <20191023141912.29110-1-lijiang@redhat.com> References: <20191023141912.29110-1-lijiang@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-MC-Unique: ZuOZjN2XOXe4_UlW_M-Jbw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kdump kernel will reuse the first 640k region because the real mode trampoline has to work in this area. When the vmcore is dumped, the old memory in this area may be accessed, therefore, kernel has to copy the contents of the first 640k area to a backup region so that kdump kernel can read the old memory from the backup area of the first 640k area, which is done in the purgatory(). But, the current handling of copying the first 640k area runs into problems when SME is enabled, kernel does not properly copy these old memory to the backup area in the purgatory(), thereby, kdump kernel reads out the encrypted contents, because the kdump kernel must access the first kernel's memory with the encryption bit set when SME is enabled in the first kernel. Please refer to this link: Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=3D204793 Finally, it causes the following errors, and the crash tool gets invalid pointers when parsing the vmcore. crash> kmem -s|grep -i invalid kmem: dma-kmalloc-512: slab:ffffd77680001c00 invalid freepointer:a6086ac099= f0c5a4 kmem: dma-kmalloc-512: slab:ffffd77680001c00 invalid freepointer:a6086ac099= f0c5a4 crash> To avoid the above errors, when the crashkernel option is specified, lets reserve the remaining low 1MiB memory(after reserving real mode memory) so that the allocated memory does not fall into the low 1MiB area, which makes us not to copy the first 640k content to a backup region in purgatory(). This indicates that it does not need to be included in crash dumps or used for anything except the processor trampolines that must live in the low 1MiB. Signed-off-by: Lianbo Jiang --- BTW:I also tried to fix the above problem in purgatory(), but there are too many restricts in purgatory() context, for example: i can't allocate new memory to create the identity mapping page table for SME situation. Currently, there are two places where the first 640k area is needed, the first one is in the find_trampoline_placement(), another one is in the reserve_real_mode(), and their content doesn't matter. In addition, also need to clean all the code related to the backup region later. arch/x86/realmode/init.c | 2 ++ include/linux/kexec.h | 2 ++ kernel/kexec_core.c | 13 +++++++++++++ 3 files changed, 17 insertions(+) diff --git a/arch/x86/realmode/init.c b/arch/x86/realmode/init.c index 7dce39c8c034..064cc79a015d 100644 --- a/arch/x86/realmode/init.c +++ b/arch/x86/realmode/init.c @@ -3,6 +3,7 @@ #include #include #include +#include =20 #include #include @@ -34,6 +35,7 @@ void __init reserve_real_mode(void) =20 =09memblock_reserve(mem, size); =09set_real_mode_mem(mem); +=09kexec_reserve_low_1MiB(); } =20 static void __init setup_real_mode(void) diff --git a/include/linux/kexec.h b/include/linux/kexec.h index 1776eb2e43a4..30acf1d738bc 100644 --- a/include/linux/kexec.h +++ b/include/linux/kexec.h @@ -306,6 +306,7 @@ extern void __crash_kexec(struct pt_regs *); extern void crash_kexec(struct pt_regs *); int kexec_should_crash(struct task_struct *); int kexec_crash_loaded(void); +void __init kexec_reserve_low_1MiB(void); void crash_save_cpu(struct pt_regs *regs, int cpu); extern int kimage_crash_copy_vmcoreinfo(struct kimage *image); =20 @@ -397,6 +398,7 @@ static inline void __crash_kexec(struct pt_regs *regs) = { } static inline void crash_kexec(struct pt_regs *regs) { } static inline int kexec_should_crash(struct task_struct *p) { return 0; } static inline int kexec_crash_loaded(void) { return 0; } +static inline void __init kexec_reserve_low_1MiB(void) { } #define kexec_in_progress false #endif /* CONFIG_KEXEC_CORE */ =20 diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c index 15d70a90b50d..5bd89f1fee42 100644 --- a/kernel/kexec_core.c +++ b/kernel/kexec_core.c @@ -37,6 +37,7 @@ #include #include #include +#include =20 #include #include @@ -70,6 +71,18 @@ struct resource crashk_low_res =3D { =09.desc =3D IORES_DESC_CRASH_KERNEL }; =20 +/* + * When the crashkernel option is specified, only use the low + * 1MiB for the real mode trampoline. + */ +void __init kexec_reserve_low_1MiB(void) +{ +=09if (strstr(boot_command_line, "crashkernel=3D")) { +=09=09memblock_reserve(0, 1<<20); +=09=09pr_info("Reserving the low 1MiB of memory for crashkernel\n"); +=09} +} + int kexec_should_crash(struct task_struct *p) { =09/* --=20 2.17.1