Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3308722ybg; Fri, 25 Oct 2019 02:08:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqy6tUzyO3wwjpIkhaJaK1WO6xfLifNedSEqEBXvLqgnD65WUtHqL2a4qFDW+j84i8MizuA6 X-Received: by 2002:a17:906:3009:: with SMTP id 9mr2426794ejz.124.1571994519736; Fri, 25 Oct 2019 02:08:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571994519; cv=none; d=google.com; s=arc-20160816; b=phy4/tSTerqmLgB9kv1DMP3myDfNkKTg6QD+GHdlr+v2vUhKja8UArGsWrBwyQiRiV Vx6jW2Ts6VejJkf7TseNa6UgOvHRWRohZ87jUoMmpejyGGNUZKQmel/BjRsZVn31HWC1 esCemTKLRrSsPbJHCEdzxu/dlbEthutrjpShIUrdwMrcvZ2egMcd1TyI66N1LLQ2vY1C 0sxQCLZV2xjp/dj6DAJvyum51wHfHPb0aK2qUKiH1mBZs1zLuBQNlo5RNF9yKErJK9fN Ie/ukwgjjw/ci4R/imIs/t44bnGQoA2cj77nYiQujCxYCn1vGBtPAMhvf+rg3bVcYQIk b4eA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=lIFLfDfjBnCHO9wGvwrjWD1QKeFnwmfjzMZGsKDtHiE=; b=d1geedKP4n9YkbgEjW3sGRUcaRwzxzveYFMrkZN5UswDU98XGuFvQ2MM1puVRpbO+F rJ++1Xi1B7xjPlUQBWTRavZ71KC7/lHgSDt5m/uzsLBRbxMN6zPD22evkgKI5FCtIN+J pP4LLyMMe869Q+6mFPsCe+65VyBuWk9HbltUveoA/FwvsvjOCrdUBqGk+YCsQfSGRM2r zznTC1lUlKDyk+nHoxAl9zVmrVDRlHOxOhDQ9h1A1svjojRsHk/o7CSww8FrcGOQs+rS diZcpm8p9Et4tR9iMrse6+rpaFJcsJT3WfbcBqrp3jtb08LLxPmM0rfuU7JaJteNluMM 2lqA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=YyAQz0JI; 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 y11si853676ejw.201.2019.10.25.02.08.15; Fri, 25 Oct 2019 02:08:39 -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=YyAQz0JI; 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 S2409166AbfJXLd7 (ORCPT + 99 others); Thu, 24 Oct 2019 07:33:59 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:43044 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725283AbfJXLd7 (ORCPT ); Thu, 24 Oct 2019 07:33:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571916837; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lIFLfDfjBnCHO9wGvwrjWD1QKeFnwmfjzMZGsKDtHiE=; b=YyAQz0JI1iqRUy4abX2fYDbJv7t6rxfG+JkzoRmLOEX8ibLFFcjVxPPY6Bl+mCVxcesBAP Xno2MDUptemymfa8xAwRytNqorTcByS8KgUY9mWTs0nvnl0qlElS7fUHXnTL/qDxTPbcGr 9pcqNAdwIieA+7OR4us7mvTz72m5OCY= 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-170-qkC7PKaAN_-m9BQX-UDVhg-1; Thu, 24 Oct 2019 07:33:51 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2A82C107AD31; Thu, 24 Oct 2019 11:33:50 +0000 (UTC) Received: from localhost.localdomain (ovpn-12-33.pek2.redhat.com [10.72.12.33]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 688FE60852; Thu, 24 Oct 2019 11:33:32 +0000 (UTC) Subject: Re: [PATCH 1/2 v5] x86/kdump: always reserve the low 1MiB when the crashkernel option is specified To: Simon Horman Cc: linux-kernel@vger.kernel.org, jgross@suse.com, Thomas.Lendacky@amd.com, bhe@redhat.com, x86@kernel.org, kexec@lists.infradead.org, dhowells@redhat.com, mingo@redhat.com, bp@alien8.de, ebiederm@xmission.com, hpa@zytor.com, tglx@linutronix.de, dyoung@redhat.com, vgoyal@redhat.com, d.hatayama@fujitsu.com, "d.hatayama@fujitsu.com" References: <20191023141912.29110-1-lijiang@redhat.com> <20191023141912.29110-2-lijiang@redhat.com> <20191024100719.GC11441@verge.net.au> From: lijiang Message-ID: <4c1c4b78-23f0-a2b9-4be7-5bab0335f10a@redhat.com> Date: Thu, 24 Oct 2019 19:33:28 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20191024100719.GC11441@verge.net.au> Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-MC-Unique: qkC7PKaAN_-m9BQX-UDVhg-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org =E5=9C=A8 2019=E5=B9=B410=E6=9C=8824=E6=97=A5 18:07, Simon Horman =E5=86=99= =E9=81=93: > Hi Linbo, >=20 > thanks for your patch. >=20 > On Wed, Oct 23, 2019 at 10:19:11PM +0800, Lianbo Jiang wrote: >> 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:a6086ac= 099f0c5a4 >> kmem: dma-kmalloc-512: slab:ffffd77680001c00 invalid freepointer:a6086ac= 099f0c5a4 >> 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 *reg= s) { } >> 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")) { >=20 > Could you comment on the issue of using strstr which > was raised by Hatayama-san in response to an earlier revision > of this patch? >=20 Thank you, Simon and Hatayama-san. Lets talk about it here. > strstr() matches for example, ANYEXTRACHARACTERScrashkernel=3DANYEXTRACHA= RACTERS. >=20 > Is it enough to use cmdline_find_option_bool()? >=20 The cmdline_find_option_bool() will find a boolean option, but the crashker= nel option is not a boolean option, maybe it looks odd. So, should we use the cmdline_= find_option() better? +#include void __init kexec_reserve_low_1MiB(void) { - if (strstr(boot_command_line, "crashkernel=3D")) { + char buffer[4]; + + if (cmdline_find_option(boot_command_line, "crashkernel=3D", + buffer, sizeof(buffer))) { memblock_reserve(0, 1<<20); pr_info("Reserving the low 1MiB of memory for crashkernel\n= "); } And here, no need to parse the arguments of crashkernel(sometimes, which ha= s a complicated syntax), so the size of buffer should be enough. What's your op= inion? Thanks Lianbo > Thanks in advance! >=20 >> +=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 >> >> >> _______________________________________________ >> kexec mailing list >> kexec@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/kexec >>