Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp620216imu; Fri, 11 Jan 2019 06:19:28 -0800 (PST) X-Google-Smtp-Source: ALg8bN5uiA6sIDgOn9BLUbjU+Wknj4k+izG/y/PpoQLFEDQ5gLVIdlWOw/6D24B5qY9B/J4QBxwC X-Received: by 2002:a17:902:7005:: with SMTP id y5mr14937505plk.7.1547216368425; Fri, 11 Jan 2019 06:19:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547216368; cv=none; d=google.com; s=arc-20160816; b=ao1GLZStELMv/IeBFpVCxP7XroNICJiR8EpTphK8NV81sbCd1sa1KXa/z4JP2VFJUe vQJn5VSrY9lAjxpWKmyLGA9X4f1F5zqcoqmaVQRAgmU2Vm5ZgqbVA88SQxWOSUtL/dbH IRbVny/UO6ho6ghDxW7OdmajYQMUoKWdticnNtNSv7aNMehsq/bv1c/y4a8654HPSC5j DqVGOODVptv5Zjl7aosbjQem+0UdITB5ZtXqlPpIoZQz8d9SJ6pJ0mpFUiCH43wsLRmQ TM386CjpJa7+Ro3WDEOPJRGwwR5FELuhVl9CLXcXKVVPFNVcL4tYD6A8hu3OKxO6GjcN djug== 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:dkim-signature; bh=JYN6qDQvtPPPCKoedb2bCKmSonRtOssz3bneax6/GbE=; b=xETh/aOY5pY4+RnFoZWCKJOWZ/PMGp1QWcITWzavB7uSI0mDUb4y/yFeeN4V61ncFJ GS9rxkCtx4XGOrXMS8AaifkFEttG7lLNvtiFq6+3dkcdpTmLQKOIJ4dxNLf/LH3uhPPC q8mSW6WjMGNwWJsrur0EVreVxsP1yMJWDhDgqJ+6p2ocdEgoC5xcNCWfnEtHLvgtoqlF TWkhiADi4M/WGiky9Ex15qWBF5BsUay/48awPv/sGILWlfbzuQ01S2TJFwTWBcQHkI2P jck2M9Cw9eqdaxsQwYAkoBK92lvsGJ9JevCMjOqS2x9JVeSpyOCHfjSmpVvqHN38ELc7 vHEw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=l596ly5w; 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=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x64si7355419pfx.87.2019.01.11.06.19.12; Fri, 11 Jan 2019 06:19:28 -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; dkim=pass header.i=@alien8.de header.s=dkim header.b=l596ly5w; 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=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732364AbfAKMdL (ORCPT + 99 others); Fri, 11 Jan 2019 07:33:11 -0500 Received: from mail.skyhub.de ([5.9.137.197]:58780 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725298AbfAKMdK (ORCPT ); Fri, 11 Jan 2019 07:33:10 -0500 Received: from zn.tnic (p200300EC2BCAC50001F60DFCC2EB2B0F.dip0.t-ipconnect.de [IPv6:2003:ec:2bca:c500:1f6:dfc:c2eb:2b0f]) (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 AF7111EC027A; Fri, 11 Jan 2019 13:33:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1547209988; 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:in-reply-to:in-reply-to: references:references; bh=JYN6qDQvtPPPCKoedb2bCKmSonRtOssz3bneax6/GbE=; b=l596ly5wdtUuAZVnea1bTmE9hO3stcTrx+0pV2i9FtpC/m9S4OA8I7/hT9xAShAPfJG5ME eLNPQEXSZdHmXPP+2AhfXS/MlCFQpPQLoCI4BScH+AYfFMYKnp30tQsl6Ee82c96D6oD2V 19BL1DOjV8p/V48V9RKcswEcHz8lG/M= Date: Fri, 11 Jan 2019 13:33:00 +0100 From: Borislav Petkov To: Lianbo Jiang 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 Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Message-ID: <20190111123300.GE4729@zn.tnic> References: <20190110121944.6050-1-lijiang@redhat.com> <20190110121944.6050-2-lijiang@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190110121944.6050-2-lijiang@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?" -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.