Re: [GIT PULL] Kbuild updates for 4.18 (2nd round)

Linus Torvalds writes: (Summary) I used to have
I used to have
CONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_CC_STACKPROTECTOR_AUTO=y
CONFIG_CC_STACKPROTECTOR_AUTO=y
which means that since my compiler supports -fstack-protector-strong, I should get CONFIG_CC_STACKPROTECTOR_STRONG.
I should get CONFIG_CC_STACKPROTECTOR_STRONG.
But that's not at all what I get. I get
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_HAS_STACKPROTECTOR_NONE=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
ie CONFIG_CC_STACKPROTECTOR_STRONG basically went away.