Re: [Security] proactive defense: using read-only memory, RO/NX modules

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Thursday, November 11, 2010 - 2:07 am

* Kees Cook <kees.cook@canonical.com> wrote:


Yeah. Please port them to latest -tip:

   http://people.redhat.com/mingo/tip.git/README

And give them some testing, and send out the new series. I'll re-report the crash to 
you for a new kernel, if it still occurs.

(Please also keep Rusty and Linus Cc:-ed for the module bits.)

In hindsight, i think the kernel/module.c bits should be in arch/x86/kernel/module.c 
- the new code is full of x86 only names and facilities.

Also, please remove various checkpatch col80 artifacts, such as:

+               if (end_pfn > begin_pfn)
+                       set_memory_nx(begin_pfn << PAGE_SHIFT,
+                                               end_pfn - begin_pfn);

that should be:

+               if (end_pfn > begin_pfn)
+                       set_memory_nx(begin_pfn << PAGE_SHIFT, end_pfn - begin_pfn);

Thanks,

	Ingo
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [Security] proactive defense: using read-only memory, ..., Ingo Molnar, (Thu Nov 11, 2:07 am)
Re: [Security] proactive defense: using read-only memory, ..., matthieu castet, (Sat Nov 13, 12:59 pm)
Re: [Security] proactive defense: using read-only memory, Valdis.Kletnieks, (Wed Nov 17, 5:12 pm)