Commit:     2c020a99e058cdfc3a073cbfbfcc6ff55d3bfc43
Parent:     f9cb02b0be4de3c51edfdd701754e13d9a2d20d6
Author:     Linus Torvalds <[EMAIL PROTECTED]>
AuthorDate: Fri Feb 22 08:21:38 2008 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Fri Feb 22 08:21:38 2008 -0800

    It's always been broken, but recent fixes actually made it do something,
    and now the brokenness shows up as the resulting kernel simply not
    working at all.
    So it used to be that you could enable this config option, and it just
    didn't do anything.  Now we'd better stop people from enabling it by
    mistake, since it _does_ do something, but does it so badly as to be
    Code to actually make it work is pending, but incomplete and won't be
    merged into 2.6.25 in any case.
    Acked-by: Arjan van de Ven <[EMAIL PROTECTED]>
    Acked-by: Sam Ravnborg <[EMAIL PROTECTED]>
    Cc: James Morris <[EMAIL PROTECTED]>
    Cc: Ingo Molnar <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 arch/x86/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 3be2305..4a88cf7 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1054,7 +1054,7 @@ config SECCOMP
        bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
-       depends on X86_64 && EXPERIMENTAL
+       depends on X86_64 && EXPERIMENTAL && BROKEN
          This option turns on the -fstack-protector GCC feature. This
          feature puts, at the beginning of critical functions, a canary
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to