x86: mm: use ARCH_HAS_DEBUG_WX instead of arch defined

[linux-2.6-block.git] / arch / x86 / Kconfig.debug

diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index f909d3ce36e6e289d8077715b18cc63de9a45f56..fdf1431ac8c2263af42dec3ae354f2c6daa1cc68 100644 (file)
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -72,33 +72,6 @@ config EFI_PGT_DUMP
          issues with the mapping of the EFI runtime regions into that
          table.
 
-config DEBUG_WX
-       bool "Warn on W+X mappings at boot"
-       select PTDUMP_CORE
-       ---help---
-         Generate a warning if any W+X mappings are found at boot.
-
-         This is useful for discovering cases where the kernel is leaving
-         W+X mappings after applying NX, as such mappings are a security risk.
-
-         Look for a message in dmesg output like this:
-
-           x86/mm: Checked W+X mappings: passed, no W+X pages found.
-
-         or like this, if the check failed:
-
-           x86/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
-
-         Note that even if the check fails, your kernel is possibly
-         still fine, as W+X mappings are not a security hole in
-         themselves, what they do is that they make the exploitation
-         of other unfixed kernel bugs easier.
-
-         There is no runtime or memory usage effect of this option
-         once the kernel has booted up - it's a one time check.
-
-         If in doubt, say "Y".
-
 config DEBUG_TLBFLUSH
        bool "Set upper limit of TLB entries to flush one-by-one"
        depends on DEBUG_KERNEL