summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorArvind Sankar <nivedita@alum.mit.edu>2020-06-16 18:25:47 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2020-06-16 17:05:07 -0700
commitff58155ca4fa7e931f34d948fa09fe14c6a66116 (patch)
tree003f3813749884ce41708c81e03658a6de88bdf5 /fs
parent651220e2aee3ccfd986a0436b8d6f5b3b5574d1f (diff)
downloadlinux-ff58155ca4fa7e931f34d948fa09fe14c6a66116.tar.gz
linux-ff58155ca4fa7e931f34d948fa09fe14c6a66116.tar.bz2
linux-ff58155ca4fa7e931f34d948fa09fe14c6a66116.zip
x86/purgatory: Add -fno-stack-protector
The purgatory Makefile removes -fstack-protector options if they were configured in, but does not currently add -fno-stack-protector. If gcc was configured with the --enable-default-ssp configure option, this results in the stack protector still being enabled for the purgatory (absent distro-specific specs files that might disable it again for freestanding compilations), if the main kernel is being compiled with stack protection enabled (if it's disabled for the main kernel, the top-level Makefile will add -fno-stack-protector). This will break the build since commit e4160b2e4b02 ("x86/purgatory: Fail the build if purgatory.ro has missing symbols") and prior to that would have caused runtime failure when trying to use kexec. Explicitly add -fno-stack-protector to avoid this, as done in other Makefiles that need to disable the stack protector. Reported-by: Gabriel C <nix.or.die@googlemail.com> Signed-off-by: Arvind Sankar <nivedita@alum.mit.edu> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions