From: Borislav Petkov <bp@alien8.de>
To: Lianbo Jiang <lijiang@redhat.com>
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
Date: Fri, 11 Jan 2019 13:33:00 +0100 [thread overview]
Message-ID: <20190111123300.GE4729@zn.tnic> (raw)
In-Reply-To: <20190110121944.6050-2-lijiang@redhat.com>
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.
next prev parent reply other threads:[~2019-01-11 12:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 12:19 [PATCH 0/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2019-01-10 12:19 ` [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Lianbo Jiang
2019-01-11 12:33 ` Borislav Petkov [this message]
2019-01-14 1:52 ` lijiang
2019-01-14 9:10 ` Borislav Petkov
2019-01-14 17:48 ` Kazuhito Hagio
2019-01-14 18:01 ` Borislav Petkov
2019-01-14 18:58 ` Dave Anderson
2019-01-14 19:21 ` Borislav Petkov
2019-01-14 19:36 ` Dave Anderson
2019-01-14 19:59 ` Borislav Petkov
2019-01-14 20:07 ` Dave Anderson
2019-01-14 20:18 ` Borislav Petkov
2019-01-14 20:26 ` Dave Anderson
2019-01-14 20:35 ` Borislav Petkov
2019-01-14 20:49 ` Dave Anderson
2019-01-15 10:06 ` Borislav Petkov
2019-01-15 11:00 ` lijiang
2019-01-11 14:56 ` Borislav Petkov
2019-01-14 5:30 ` lijiang
2019-01-14 9:15 ` Borislav Petkov
2019-01-15 9:41 ` lijiang
2019-01-15 10:09 ` [tip:x86/kdump] kdump: Document kernel data exported in the vmcoreinfo note tip-bot for Lianbo Jiang
2019-01-10 12:19 ` [PATCH 2/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2019-01-11 15:15 ` [tip:x86/kdump] x86/kdump: Export the SME " tip-bot for Lianbo Jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190111123300.GE4729@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=anderson@redhat.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).