| 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: Mon, 12 Mar 2012 17:42:18 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Jan Kratochvil <jan.kratochvil@...hat.com> CC: Denys Vlasenko <dvlasenk@...hat.com>, Roland McGrath <roland@...k.frob.com>, linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>, Kushal Das <kdas@...hat.com> Subject: Re: Extending coredump note section to contain filenames On 03/12/2012 05:36 PM, Jan Kratochvil wrote: > On Tue, 13 Mar 2012 01:31:43 +0100, H. Peter Anvin wrote: >> This is basically providing the dso_list and executable information. >> Several of the other things you list above (cmdline, environ, pid, >> reason, maps) are already part of a core file. > > dso_list and executable identification (their build-id) are also part of the > core file. It is only filesystem defect it can map filename -> content but it > cannot map build-id -> content. There are many indexing solutions for it, > including slocate, when you have started to talk about not 100% reliable > solutions. There is no 100% reliable solution possible -- you have no guarantee of any kind that the library executable still exists. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- 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