linux-kernel - Re: [PATCH 0/4] kcore: cleanup and fix bahavior to find physcal memory range v2

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:	Wed, 22 Jul 2009 13:52:32 +0800
From:	Amerigo Wang <xiyou.wangcong@...il.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/4] kcore: cleanup and fix bahavior to find physcal
	memory range v2

On Wed, Jul 22, 2009 at 02:06:13PM +0900, KAMEZAWA Hiroyuki wrote:
>I'm sorry I can't find who should be in CC.
>

Just keep the original CC's, or run scripts/get_maintainer.pl -f fs/proc/kcore.c.
:-)


>This includes some amounts changes to arch-specici code, 
>but very special codes for kcore. Can I test this in -mm if no objections ?
>
>Now, /proc/kcore 's physical memory information is set up at boot
>via kclist_add(). But it's not updated at memory hotplug etc and
>it can include much memory holes. This patch is for generatinc /proc/kcore
>based on memory management information maintained by the kernel.
>
> For usual archs, /proc/iomem is used
> For ppc, lmb information will be used.
>

This is a good idea!
--
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/