This was not an issue in the kernel; rather the qa-regression-testing
script needed to take into account the auto-detection of the compiler's
ability to perform stack protection and the restructuring of the config
option due to that. I have fixed this in https://git.launchpad.net/qa-
regression-testing/commit/?id=69b1392a208985e90857facbe367e3af635c8228 .
Unfortunately, it looks to change a bit again in the 4.18 kernel, but I
think I have the checks set up to work properly when that lands as well.
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Invalid
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Changed in: qa-regression-testing
Assignee: (unassigned) => Steve Beattie (sbeattie)
** Changed in: qa-regression-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776242
Title:
CONFIG_CC_STACKPROTECTOR is now defined on Makefile
Status in QA Regression Testing:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Cosmic:
Invalid
Bug description:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic-canonical-kernel-team-
bootstrap/cosmic/amd64/l/linux/20180524_171024_2701c@/log.gz
15:41:48 ERROR| [stderr] CONFIG_CC_STACKPROTECTOR set ... FAIL
commit 2bc2f688fdf8808de4f36be563ccdb0bde7c0c54
Makefile: move stack-protector availability out of Kconfig
+ ifndef stackp-broken
+ # If the stack protector is functional, enable code that depends on it.
+ KBUILD_CPPFLAGS += -DCONFIG_CC_STACKPROTECTOR
+ endif
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1776242/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
