[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <249444.1325030069@turing-police.cc.vt.edu>
Date: Tue, 27 Dec 2011 18:54:29 -0500
From: Valdis.Kletnieks@...edu
To: Cyrill Gorcunov <gorcunov@...nvz.org>
Cc: linux-kernel@...r.kernel.org,
Pavel Emelyanov <xemul@...allels.com>,
Glauber Costa <glommer@...allels.com>,
Andi Kleen <andi@...stfloor.org>, Tejun Heo <tj@...nel.org>,
Matt Helsley <matthltc@...ibm.com>,
Pekka Enberg <penberg@...nel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Vasiliy Kulikov <segoon@...nwall.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [patch 1/4] Add routine for generating an ID for kernel pointer
On Fri, 23 Dec 2011 16:47:42 +0400, Cyrill Gorcunov said:
> The routine XORs the given pointer with a random value
> producing an ID (32 or 64 bit, depending on the arch).
> Index: linux-2.6.git/mm/Kconfig
> +config GENERIC_OBJECT_ID
> + bool "Enable generic object ID infrastructure"
> + depends on CHECKPOINT_RESTORE
> + default n
> + help
> + Turn on the functionality that can generate IDs for kernel
"Turn on functionality"
> + objects, which are exported to userspace via /proc filesystem.
Lose the ,
> +
> + It is useful if you need to examinate kernel objects and test
examine
> + if they are shared between several tasks. These IDs should never
> + be used for anything but the "sameness" test. Besides, the IDs are
s/Besides, the/The/
> + dynamic and valid only while object is alive, once it get freed or
s/alive, once/alive. Once/
> + kernel is rebooted -- the IDs will be changed.
s/ --/,/
Also, see Andrew's comments regarding a generic foo_fields_equal() in-kernel.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists