Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3073325imu; Sun, 13 Jan 2019 17:53:43 -0800 (PST) X-Google-Smtp-Source: ALg8bN6qd60GQiiXK00Ju+FO+mq/rysTRpI8/XhiHQojEVfKNGJ3gdoMJZ3HKZExNMZ/DW9LCDWi X-Received: by 2002:a63:4611:: with SMTP id t17mr21083443pga.119.1547430823812; Sun, 13 Jan 2019 17:53:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547430823; cv=none; d=google.com; s=arc-20160816; b=Xbb8lNGhzRCBPI2wK2qAda9QuG/ORwWGLR1/vfj6gT/lWn8Rjdu7Cc27/rEy3GKWgp d5CV0icXw8mg29DCOXxo7FEUUajWt+4oViVQ5fHkwHRGkUPaxKmpLXFwbhByNFaQ2i3z GneX+zV5by4sTvW2momItDOmFbAu25W8aewiIezjEBOm/ia3OyJO3E13QVAiexGajT7e hI+k4L+FpyP4CpV+8t2U/9QswK4z2Nv03UmJuUrZYhShnz7kzDo9IXOleIDrTto9LAKI tQ9hXCMj2+5cTU88YTXYI37cPZdL6PaSmHKmcVVlUuHxX/gvfxE4siN/YVzUDkt3spjr O/jw== 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; bh=cE3hgR1NGwlk/1Mfq+ytsQcYcjWqxVDN7e1i+MnVy90=; b=FnHss8jld9j+wVDJyJNeAff32vSmOS8X9pGJxbqMfwYkBzrtMnzpAmKbyHITQiJ/Ld a47AbK3QwaJu5R6tPb0lOYhVulANibsuDmatutFdIuw5zer2S2SBK682z0VQoyXDF9GB +0qf77tM2iKpTCDk1oD8IWgM/NC4BFkDaqyurol2r9nCdiTuYDdBsW+lcdlTPJ1lZxVR 3hGyoJ9uig++TkKMXPTHgMywdXlwxD5a11r4St00oKNpUO2JDQ2Okklu2LXGk9A9uYYG OZUmcyZmjDtKyxcn+4naercQUt0R4gieHJQI3O3eoAtckpFHA044nsKy4zF4bqcFYeEW pvBA== 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 z6si74490439pgl.109.2019.01.13.17.53.28; Sun, 13 Jan 2019 17:53:43 -0800 (PST) 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 S1726698AbfANBw1 (ORCPT + 99 others); Sun, 13 Jan 2019 20:52:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50878 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726631AbfANBw0 (ORCPT ); Sun, 13 Jan 2019 20:52:26 -0500 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 mx1.redhat.com (Postfix) with ESMTPS id 784DA80F6D; Mon, 14 Jan 2019 01:52:26 +0000 (UTC) Received: from localhost.localdomain (ovpn-12-115.pek2.redhat.com [10.72.12.115]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D4900183D8; Mon, 14 Jan 2019 01:52:18 +0000 (UTC) Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation To: Borislav Petkov Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, akpm@linux-foundation.org, bhe@redhat.com, dyoung@redhat.com, k-hagio@ab.jp.nec.com, anderson@redhat.com, linux-doc@vger.kernel.org References: <20190110121944.6050-1-lijiang@redhat.com> <20190110121944.6050-2-lijiang@redhat.com> <20190111123300.GE4729@zn.tnic> From: lijiang Message-ID: <93c1969f-dcc7-4e34-75ff-b14f2ec15269@redhat.com> Date: Mon, 14 Jan 2019 09:52:14 +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: <20190111123300.GE4729@zn.tnic> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Mon, 14 Jan 2019 01:52:26 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2019年01月11日 20:33, Borislav Petkov 写道: > On Thu, Jan 10, 2019 at 08:19:43PM +0800, Lianbo Jiang wrote: >> +init_uts_ns.name.release >> +------------------------ >> + >> +The version of the Linux kernel. Used to find the corresponding source >> +code from which the kernel has been built. >> + > > ... > >> + >> +init_uts_ns >> +----------- >> + >> +This is the UTS namespace, which is used to isolate two specific >> +elements of the system that relate to the uname(2) system call. The UTS >> +namespace is named after the data structure used to store information >> +returned by the uname(2) system call. >> + >> +User-space tools can get the kernel name, host name, kernel release >> +number, kernel version, architecture name and OS type from it. > > Already asked this but no reply so lemme paste my question again: > > "And this document already fulfills its purpose - those two vmcoreinfo > exports are redundant and the first one can be removed. > > And now that we agreed that VMCOREINFO is not an ABI and is very tightly > coupled to the kernel version, init_uts_ns.name.release can be removed, > yes? > > Or is there anything speaking against that?" > Sorry for this, that is my mistake. Thanks for your reminder. I agree on your point of view. But i forgot that i should remove this variable in this post. I would like to remove this variable and post again. Thanks. Lianbo