From: Dave Anderson <anderson@redhat.com> To: Borislav Petkov <bp@alien8.de> Cc: Kazuhito Hagio <k-hagio@ab.jp.nec.com>, Lianbo Jiang <lijiang@redhat.com>, 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, linux-doc@vger.kernel.org Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Date: Mon, 14 Jan 2019 15:26:32 -0500 (EST) [thread overview] Message-ID: <221183717.69773903.1547497592624.JavaMail.zimbra@redhat.com> (raw) In-Reply-To: <20190114201812.GT2773@zn.tnic> ----- Original Message ----- > On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote: > > That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and > > pulls out the OSRELEASE string from it, so that a user can determine what > > vmlinux file should be used with that vmcore for normal crash analysis. > > And the vmcoreinfo is part of the vmcore, right? Correct. > > So it can just as well read out the address of init_uts_ns and get the > kernel version from there. No. It needs *both* the vmlinux file and the vmcore file in order to read kernel virtual memory, so just having a kernel virtual address is insufficient. So it's a chicken-and-egg situation. This particular --osrelease option is used to determine *what* vmlinux file would be required for an actual crash analysis session. Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Anderson <anderson@redhat.com> To: Borislav Petkov <bp@alien8.de> Cc: Kazuhito Hagio <k-hagio@ab.jp.nec.com>, Lianbo Jiang <lijiang@redhat.com>, bhe@redhat.com, linux-doc@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, mingo@redhat.com, tglx@linutronix.de, dyoung@redhat.com, akpm@linux-foundation.org Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Date: Mon, 14 Jan 2019 15:26:32 -0500 (EST) [thread overview] Message-ID: <221183717.69773903.1547497592624.JavaMail.zimbra@redhat.com> (raw) In-Reply-To: <20190114201812.GT2773@zn.tnic> ----- Original Message ----- > On Mon, Jan 14, 2019 at 03:07:33PM -0500, Dave Anderson wrote: > > That's what it *does* utilize -- it takes a standalone vmcore dumpfile, and > > pulls out the OSRELEASE string from it, so that a user can determine what > > vmlinux file should be used with that vmcore for normal crash analysis. > > And the vmcoreinfo is part of the vmcore, right? Correct. > > So it can just as well read out the address of init_uts_ns and get the > kernel version from there. No. It needs *both* the vmlinux file and the vmcore file in order to read kernel virtual memory, so just having a kernel virtual address is insufficient. So it's a chicken-and-egg situation. This particular --osrelease option is used to determine *what* vmlinux file would be required for an actual crash analysis session. Dave _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-01-14 20:26 UTC|newest] Thread overview: 48+ 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 0/2 v6] kdump, vmcoreinfo: " Lianbo Jiang 2019-01-10 12:19 ` [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Lianbo Jiang 2019-01-10 12:19 ` Lianbo Jiang 2019-01-11 12:33 ` Borislav Petkov 2019-01-11 12:33 ` Borislav Petkov 2019-01-14 1:52 ` lijiang 2019-01-14 1:52 ` lijiang 2019-01-14 9:10 ` Borislav Petkov 2019-01-14 9:10 ` Borislav Petkov 2019-01-14 17:48 ` Kazuhito Hagio 2019-01-14 17:48 ` Kazuhito Hagio 2019-01-14 18:01 ` Borislav Petkov 2019-01-14 18:01 ` Borislav Petkov 2019-01-14 18:58 ` Dave Anderson 2019-01-14 18:58 ` Dave Anderson 2019-01-14 19:21 ` Borislav Petkov 2019-01-14 19:21 ` Borislav Petkov 2019-01-14 19:36 ` Dave Anderson 2019-01-14 19:36 ` Dave Anderson 2019-01-14 19:59 ` Borislav Petkov 2019-01-14 19:59 ` Borislav Petkov 2019-01-14 20:07 ` Dave Anderson 2019-01-14 20:07 ` Dave Anderson 2019-01-14 20:18 ` Borislav Petkov 2019-01-14 20:18 ` Borislav Petkov 2019-01-14 20:26 ` Dave Anderson [this message] 2019-01-14 20:26 ` Dave Anderson 2019-01-14 20:35 ` Borislav Petkov 2019-01-14 20:35 ` Borislav Petkov 2019-01-14 20:49 ` Dave Anderson 2019-01-14 20:49 ` Dave Anderson 2019-01-15 10:06 ` Borislav Petkov 2019-01-15 10:06 ` Borislav Petkov 2019-01-15 11:00 ` lijiang 2019-01-15 11:00 ` lijiang 2019-01-11 14:56 ` Borislav Petkov 2019-01-11 14:56 ` Borislav Petkov 2019-01-14 5:30 ` lijiang 2019-01-14 5:30 ` lijiang 2019-01-14 9:15 ` Borislav Petkov 2019-01-14 9:15 ` Borislav Petkov 2019-01-15 9:41 ` lijiang 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-10 12:19 ` [PATCH 2/2 v6] kdump, 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=221183717.69773903.1547497592624.JavaMail.zimbra@redhat.com \ --to=anderson@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=bhe@redhat.com \ --cc=bp@alien8.de \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.