lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20190114203500.GU2773@zn.tnic> Date: Mon, 14 Jan 2019 21:35:00 +0100 From: Borislav Petkov <bp@...en8.de> To: Dave Anderson <anderson@...hat.com> Cc: Kazuhito Hagio <k-hagio@...jp.nec.com>, Lianbo Jiang <lijiang@...hat.com>, linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, tglx@...utronix.de, mingo@...hat.com, x86@...nel.org, akpm@...ux-foundation.org, bhe@...hat.com, dyoung@...hat.com, linux-doc@...r.kernel.org Subject: Re: [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation On Mon, Jan 14, 2019 at 03:26:32PM -0500, Dave Anderson wrote: > 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. Ok, that makes sense. I could've used that explanation when reviewing the documentation. Do you mind skimming through this: https://lkml.kernel.org/r/20190111145650.GG4729@zn.tnic in case we've missed explaining relevant usage - like that above - of some of the vmcoreinfo members? Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists