lkml.org 
[lkml]   [2009]   [Feb]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Using module private memory to simulate microkernel's memory protection

* Pengfei Hu <hpfei.cn@gmail.com> wrote:

> diff -Nurp old/arch/x86/Kconfig.debug new/arch/x86/Kconfig.debug
> --- old/arch/x86/Kconfig.debug 2008-10-10 06:13:53.000000000 +0800
> +++ new/arch/x86/Kconfig.debug 2008-12-07 19:19:40.000000000 +0800
> @@ -67,6 +67,16 @@ config DEBUG_PAGEALLOC
> This results in a large slowdown, but helps to find certain types
> of memory corruptions.
>
> +config DEBUG_KM_PROTECT
> + bool "Debug kernel memory protect"
> + depends on DEBUG_KERNEL
> + select DEBUG_PAGEALLOC
> + select SLUB
> + help
> + Change page table's present flag to prevent other module's accidental
> + access. This results in a large slowdown and waste more memory, but
> + helps to find certain types of memory corruptions.

Hm, are you aware of the kmemcheck project?

Ingo


\
 
 \ /
  Last update: 2009-02-10 15:17    [W:0.107 / U:0.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site