linux-kernel - Re: mmap'ed memory in core files ?

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]

Message-ID: <20080702133013.GA1848@infradead.org>
Date:	Wed, 2 Jul 2008 09:30:13 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Philippe De Muyter <phdm@...qel.be>
Cc:	Michael Kerrisk <mtk.manpages@...il.com>,
	linux-kernel@...r.kernel.org, libdc1394-devel@...ts.sourceforge.net
Subject: Re: mmap'ed memory in core files ?

On Wed, Jul 02, 2008 at 12:50:27PM +0200, Philippe De Muyter wrote:
> Unfortunately, the part that applies to me (I have tested it) is the next one :
> 
>     Memory-mapped I/O pages such as frame buffer are never dumped, [...],
>     regardless of the coredump_filter value.
> 
> Is that a design decision, or a mere finding of the way it is implemented
> now ?

It's an implementation issue, and there are patches queue for 2.6.27
that allow gdb access to these regions, which should be easily
extendable to cover core dumps, too.

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