linux-kernel - Re: Extending coredump note section to contain filenames

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Mar 2012 17:31:43 -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:27 PM, Jan Kratochvil wrote:
> On Tue, 13 Mar 2012 01:16:30 +0100, H. Peter Anvin wrote:
>> That's quite absurd if you think about it... we're talking about each
>> individual library, not necessarily the root binary.
> 
> Denys is also working on ABRT which already dumps a lot of useful info
> associated with a core file:
> 	abrt_version analyzer architecture cmdline component coredump count
> 	dso_list environ executable hostname kernel maps os_release package
> 	pid pwd reason time uid username uuid var_log_messages
> 
> I find the local copy instances of the files of specific build the same or
> even less less useful info than those files above.
> 
> One should start implementing dumping all the info above info Linux kernel
> before the filenames are worth it.
> 

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.  The rest sounds like an
RFE to me.

	-hpa
--
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/