| 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: <20070710125904.GC22862@suse.de> Date: Tue, 10 Jul 2007 14:59:05 +0200 From: Bernhard Walle <bwalle@...e.de> To: kexec@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: Determine version of kernel that produced vmcore * Vivek Goyal <vgoyal@...ibm.com> [2007-07-10 08:36]: > > does anybody know a _reliable_ way to determine the version the kernel > > that produced a vmcore file? This means not scanning for a specific > > string or something like that which can fail on random memory. > > > > Would it make sense to add a ELF PT_NOTE section in the vmcore? > > To me it makes sense to append an ELF NOTE to vmcore which can uniquely > associate that vmcore with a particular vmlinux file (Some string > equivalent to the output of uname -a). Well, if we embed the CONFIGFILE from makedumpfile in some magic way we don't need it ... we'll see. > Interesting thing is that to find version of vmlinux, you will still be > doing <string | grep "some pattern">. Probably then we should append an > ELF note to vmlinux file also? Yes, that was my proposal some time ago, see http://article.gmane.org/gmane.comp.boot-loaders.fastboot.general/3996 Any comments on that patch are appreciated. :) Thanks, Bernhard - 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