Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1105328imd; Sat, 27 Oct 2018 02:13:03 -0700 (PDT) X-Google-Smtp-Source: AJdET5cG4vHfj0VE6IWzaR9yOsh+a0tpdCk0EOwiDzaLQfnCJJ6YbZKQ6uyvHB/FKy87F/hJpQ1W X-Received: by 2002:a62:2b41:: with SMTP id r62-v6mr216717pfr.105.1540631583194; Sat, 27 Oct 2018 02:13:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540631583; cv=none; d=google.com; s=arc-20160816; b=ChkRT3n0uWGZ90wRHVITrvmC205sWtHUiOtyWnnjVnpYyWDl7Km6bp6Uv5Yzo9DcA4 yqKn1Uv2O0ZcDRp6aIPP3GWdfTNKuiHhrKOCSAM81OZBYiEXK6gly374vsITWffcHxDJ HCGqUZIadUHYMx6GnhD/R9MQ2mGN55vr+n3XnQpYG6SsUYuEqFSibFwDdJF0CGiSop6/ zwLrkWTRvcIRWu9beUDWKDlNB2Mvt1Tt6WD4dOSR+sIIggtav67p2Jobl/iUMS7ToNMl 4zQBvXV9eE81COJWETKDzDqrDSKZJoW3YYsMShKoCB3SWWHUaay64mEMc7nyGb5dCz3O rCUg== 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=mBfn8zk8i34fXYSGpEPi99X0gddetYZc/n2TnV+Vjhg=; b=Mv65v+ABnIlREtHw+WiYUYtnpCDf4DOQahhHcqPmGef/eQPJVtj3gy1sxg7CssrsNj ZiNFjmRJ+59yeGk07Z5sLgIwrVLBmK/DguFPI3GZmCeM1fbdu9lMTFT5q4XQ1qq+8wBz Ljkt+d9el7T+37aa6dmdPH4OTZhBaw8z5ZXxUQayAPY2L64LnfBqNsaXjdeb0OszhCuB QOV8A9s9LoGVIyIVnBL1Q3LFrHbvFSO4JZdsRJZKMR1z6OUgM2szG9fyUEPDbw21QQw3 Ijb7q+QypVzazFPZQHxANBfsqrQlfosBUC3BHhYpv4MpVje0PsLeD6T7teslYYhXBydS BYnQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h8-v6si14676633pli.135.2018.10.27.02.12.47; Sat, 27 Oct 2018 02:13:03 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728269AbeJ0RuL (ORCPT + 99 others); Sat, 27 Oct 2018 13:50:11 -0400 Received: from mail.skyhub.de ([5.9.137.197]:58014 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726193AbeJ0RuL (ORCPT ); Sat, 27 Oct 2018 13:50:11 -0400 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hhj8QxL2PV8M; Sat, 27 Oct 2018 11:09:54 +0200 (CEST) Received: from nazgul.tnic (unknown [185.30.24.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id CC3AA1EC068B; Sat, 27 Oct 2018 11:09:53 +0200 (CEST) Date: Sat, 27 Oct 2018 11:10:07 +0200 From: Borislav Petkov To: Baoquan He Cc: Petr Tesarik , lijiang , linux-kernel@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, mingo@redhat.com, tglx@linutronix.de, dyoung@redhat.com Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to vmcoreinfo Message-ID: <20181027091007.GB1046@nazgul.tnic> References: <20181026093630.8520-1-lijiang@redhat.com> <053CC83A-9A95-4C12-9627-AABD1427DA9C@alien8.de> <1263471c-a27d-a698-15f0-b5947f13ea93@redhat.com> <20181026182440.20a4b107@ezekiel.suse.cz> <20181026222517.GB26927@nazgul.tnic> <20181027081343.GA1884@MiWiFi-R3L-srv> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20181027081343.GA1884@MiWiFi-R3L-srv> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 27, 2018 at 04:13:43PM +0800, Baoquan He wrote: > Yes, agree. So sme_me_mask itself or the encryption bit number, both is > fine. You need the encryption bit position and it better be properly formatted and extracted into a vmcoreinfo-specific variable because we don't expose arch-specific details like sme_me_mask to the outside. > we may use cp to copy /proc/vmcore to a file directly, then analyze > it in another compupter. This often happen when there's something > wrong with makedumpfile, we need debug makedumpfile with the complete > copied file. So for the analyze-on-another-computer scenario you absolutely must copy anything from the first kernel decrypted because you can't decrypt it on the other machine. Which means, in a sensitive environment, you probably should copy and *encrypt* the dump again with gpg or so. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --