From: Ingo Molnar <mingo@elte.hu>
To: Pengfei Hu <hpfei.cn@gmail.com>, Vegard Nossum <vegard.nossum@gmail.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Using module private memory to simulate microkernel's memory protection
Date: Tue, 10 Feb 2009 15:14:05 +0100 [thread overview]
Message-ID: <20090210141405.GA16147@elte.hu> (raw)
In-Reply-To: <a5f59d880902100542x7243b13fuf40e7dd21faf7d7a@mail.gmail.com>
* 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
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Pengfei Hu <hpfei.cn@gmail.com>, Vegard Nossum <vegard.nossum@gmail.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Using module private memory to simulate microkernel's memory protection
Date: Tue, 10 Feb 2009 15:14:05 +0100 [thread overview]
Message-ID: <20090210141405.GA16147@elte.hu> (raw)
In-Reply-To: <a5f59d880902100542x7243b13fuf40e7dd21faf7d7a@mail.gmail.com>
* 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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-10 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 13:42 Using module private memory to simulate microkernel's memory protection Pengfei Hu
2009-02-10 13:42 ` Pengfei Hu
2009-02-10 14:14 ` Ingo Molnar [this message]
2009-02-10 14:14 ` Ingo Molnar
2009-02-11 14:04 ` Pengfei Hu
2009-02-11 14:04 ` Pengfei Hu
2009-02-11 14:55 ` Ingo Molnar
2009-02-11 14:55 ` Ingo Molnar
2009-02-11 15:23 ` Ingo Molnar
2009-02-11 15:23 ` Ingo Molnar
2009-02-21 9:24 ` Pengfei Hu
2009-02-21 9:24 ` Pengfei Hu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090210141405.GA16147@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpfei.cn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.