| 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
| ||
|
Message-Id: <20090917114138.e14a1183.kamezawa.hiroyu@jp.fujitsu.com> Date: Thu, 17 Sep 2009 11:41:38 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com> Cc: Am?rico_Wang <xiyou.wangcong@...il.com>, "Andrew Morton" <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: [PATCH 0/3][mmotm] showing size of kcore (Was Re: kcore patches (was Re: 2.6.32 -mm merge plans) On Wed, 16 Sep 2009 20:17:52 +0900 (JST) "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com> wrote: > But for now, we have to use some fixed value....and using above > patch for 2.6.31 is not very bad. > This set is based on mmotm's kcore patch stack. So, just for discussing. [1/3] ... clean up (tiny bug fix) [2/3] ... show size of /proc/kcore [3/3] ... update kcore size at memory hotplug. After patches, /proc/kcore's size is as following. == [kamezawa@...extal mmotm-2.6.31-Sep14]$ ls -l /proc/kcore -r-------- 1 root root 140737486266368 2009-09-17 11:53 /proc/kcore [kamezawa@...extal mmotm-2.6.31-Sep14]$ == I'm not sure how this value is useful...but..hmm..better than zero ? (The reason of very big value is because vmalloc area is too large.) 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/
Powered by blists - more mailing lists