linux-kernel - [RFC][PATCH 0/6] kcore clean up and enhance. v3

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-next>] [day] [month] [year] [list]

Date:	Fri, 24 Jul 2009 17:08:19 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	xiyou.wangcong@...il.com,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	ralf@...ux-mips.org, benh@...nel.crashing.org, lethal@...ux-sh.org
Subject: [RFC][PATCH 0/6] kcore clean up and enhance. v3

Hi, back to RFC again. 2 patches are added.

Now, /proc/kcore is not aware of physical memory layout and has no hooks for
memory hotplug. I'm trying to fix it. But at doing so, I've wrote several
clean-up patches unexpectedly ;)

Now, /proc/kcore has per-arch hooks to x86-32/64, sh, mips, ia64,
powerpc-32/64. I think I know x86-32/64's and ia64 memory layout well,
but not sure about others. Then, I CCed to maintainers. please notify me
if any concerns.
After this, most of arch-specific codes can be removed.
(x86-64 and mips-64bit seems to have something special.)

Patches
[1/6] kcore clean up/ use usual list ops 
[2/6] kcore clean up/ add kclist type.
[3/6] kcore clean up/ unifiy per-arch vmalloc kclist_add()
[4/6] kcore clean up/ unifiy per-arch text range kclist_add()
[5/6] kcore enhance / use precise physical memory check and support hotplug.
[6/6] generic: rewrite walk_memory_resource as to be  walk_system_ram_range().

Any comments are welcome.
I'm sorry that I may not be able to make a quick reply.

Thanks,
-Kame

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