linux-kernel - Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CD6006EB.36EC%kingboard.ma@hp.com>
Date:	Fri, 8 Mar 2013 13:31:51 +0000
From:	"Ma, Jingbai (Kingboard)" <kingboard.ma@...com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Vivek Goyal <vgoyal@...hat.com>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"kumagai-atsushi@....nes.nec.co.jp" 
	<kumagai-atsushi@....nes.nec.co.jp>,
	"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
	"yinghai@...nel.org" <yinghai@...nel.org>,
	"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Mitchell, Lisa (MCLinux in Fort Collins)" <lisa.mitchell@...com>
Subject: Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel
 to speedup kernel dump process

On 3/8/13 6:33 PM, "H. Peter Anvin" <hpa@...or.com> wrote:


>On 03/08/2013 02:06 AM, Jingbai Ma wrote:
>> 
>> Kernel do have some abilities that user space haven't. It's possible to
>> map whole memory space of the first kernel into user space on the second
>> kernel. But the user space code has to re-implement some parts of the
>> kernel memory management system again. And worse, it's architecture
>> dependent, more architectures supported, more codes have to be
>> implemented. All implementation in user space must be sync to kernel
>> implementation. It's may called "flexibility", but it's painful to
>> maintain the codes.
>> 
>
>What?  You are basically talking about /dev/mem... there is nothing
>particularly magic about it at all.

What we are talking about is filtering memory pages (AKA memory pages
classification)
The makedumpfile (or any other dumper in user space) has to know the
exactly
memory layout of the memory management data structures, it not only
architecture dependent, but also may varies in different kernel release.
At this point, /dev/mem doesn't give any help.
So IMHO, I would like to do it in kernel, rather than So keep tracking
changes in user space code.

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