aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot/uboot-lantiq/patches/0026-no_extern_inline.patch
diff options
context:
space:
mode:
authorHauke Mehrtens <hauke@hauke-m.de>2021-04-03 20:02:54 +0200
committerHauke Mehrtens <hauke@hauke-m.de>2021-04-30 23:51:19 +0200
commit9ffa2f8193a43b9044fcfd0e16b204e989b0d941 (patch)
treed688599fcacdf1cdee92c8914a833410a672a4a7 /package/boot/uboot-lantiq/patches/0026-no_extern_inline.patch
parent20a924d2ae378fe35b74f81be3b7f58366472e80 (diff)
downloadupstream-9ffa2f8193a43b9044fcfd0e16b204e989b0d941.tar.gz
upstream-9ffa2f8193a43b9044fcfd0e16b204e989b0d941.tar.bz2
upstream-9ffa2f8193a43b9044fcfd0e16b204e989b0d941.zip
kernel: Activate FORTIFY_SOURCE for MIPS kernel 5.4
CONFIG_FORTIFY_SOURCE=y is already set in the generic kernel configuration, but it is not working for MIPS on kernel 5.4, support for MIPS was only added with kernel 5.5, other architectures like aarch64 support FORTIFY_SOURCE already since some time. This patch adds support for FORTIFY_SOURCE to MIPS with kernel 5.4, kernel 5.10 already supports this and needs no changes. This backports one patch from kernel 5.5 and one fix from 5.8 to make fortify source also work on our kernel 5.4. The changes are not compatible with the 306-mips_mem_functions_performance.patch patch which was also removed with kernel 5.10, probably because of the same problems. I think it is not needed anyway as the compiler should automatically optimize the calls to memset(), memcpy() and memmove() even when not explicitly telling the compiler to use the build in variant. This increases the size of an uncompressed kernel by less than 1 KB. Acked-by: Rosen Penev <rosenp@gmail.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Diffstat (limited to 'package/boot/uboot-lantiq/patches/0026-no_extern_inline.patch')
0 files changed, 0 insertions, 0 deletions