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
| ||
|
Date: Wed, 12 Nov 2014 17:12:05 -0500 From: Vivek Goyal <vgoyal@...hat.com> To: HATAYAMA Daisuke <d.hatayama@...fujitsu.com> Cc: ebiederm@...ssion.com, linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, kumagai-atsushi@....nes.nec.co.jp, anderson@...hat.com Subject: Re: [PATCH] kdump, x86: report actual value of phys_base in VMCOREINFO On Wed, Nov 12, 2014 at 03:40:42PM +0900, HATAYAMA Daisuke wrote: > Currently, VMCOREINFO note information reports the virtual address of > phys_base that is assigned to symbol phys_base. But this doesn't make > sense because to refer to value of the phys_base, it's necessary to > get the value of phys_base itself we are now about to refer to. > Hi Hatayama, /proc/vmcore ELF headers have virtual address information and using that you should be able to read actual value of phys_base. gdb deals with virtual addresses all the time and can read value of any symbol using those headers. So I am not sure what's the need for exporting actual value of phys_base. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists