Re: move stack-protector availability out of Kconfig

[tedheadster]

Kees,
  I have a question about this patch. When I configure a kernel for
ARCH=i386 it sets these Kconfig variables this way:

HAVE_CC_STACKPROTECTOR=y
CC_STACKPROTECTOR_AUTO=y

CC_STACKPROTECTOR_NONE=n
CC_STACKPROTECTOR_REGULAR=n
CC_STACKPROTECTOR_STRONG=n

It seems to me that at least _one_ of the last _three_ variables
should be set to 'y' with the defaults that are being set, probably
CC_STACKPOINTER_NONE=y. All of them being 'n' doesn't make sense to
me.

As a side note, these defaults set X86_32_LAZY_GS=n (depends on X86_32
[=y] && CC_STACKPROTECTOR_NONE [=n]) which causes the x86_32 kernels
to hang. I'll discuss  that in a different email thread, but just
wanted to say how I came upon this.

- Matthew Whitehead