diff options
author | Jan Glauber <jang@linux.vnet.ibm.com> | 2011-05-20 02:55:26 +0400 |
---|---|---|
committer | Rusty Russell <rusty@rustcorp.com.au> | 2011-05-19 11:25:26 +0400 |
commit | 448694a1d50432be63aafccb42d6f54d8cf3d02c (patch) | |
tree | bd066b7cdb04e8bdc61efdeaa0e358269f185f7e /arch/microblaze/Kconfig | |
parent | 4d10380e720a3ce19dbe88d0133f66ded07b6a8f (diff) | |
download | linux-448694a1d50432be63aafccb42d6f54d8cf3d02c.tar.xz |
module: undo module RONX protection correctly.
While debugging I stumbled over two problems in the code that protects module
pages.
First issue is that disabling the protection before freeing init or unload of
a module is not symmetric with the enablement. For instance, if pages are set
to RO the page range from module_core to module_core + core_ro_size is
protected. If a module is unloaded the page range from module_core to
module_core + core_size is set back to RW.
So pages that were not set to RO are also changed to RW.
This is not critical but IMHO it should be symmetric.
Second issue is that while set_memory_rw & set_memory_ro are used for
RO/RW changes only set_memory_nx is involved for NX/X. One would await that
the inverse function is called when the NX protection should be removed,
which is not the case here, unless I'm missing something.
Signed-off-by: Jan Glauber <jang@linux.vnet.ibm.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'arch/microblaze/Kconfig')
0 files changed, 0 insertions, 0 deletions