mbox series

[v1,0/1] ARM hangs on boot with CONFIG_FORTIFY_SOURCE and ATAGs

Message ID 20210819022144.22719-1-bfgithub@veryspeedy.net (mailing list archive)
Headers show
Series ARM hangs on boot with CONFIG_FORTIFY_SOURCE and ATAGs | expand

Message

bfgithub@veryspeedy.net Aug. 19, 2021, 2:21 a.m. UTC 
From: Berto Furth <bfgithub@veryspeedy.net>

ARM may hang on boot with ATAGS and CONFIG_FORTIFY_SOURCE.


An ARM 32 device may hang on boot after the

Uncompressing Linux... done, booting the kernel.

message if the bootloader passes a command line via ATAG to the
kernel and CONFIG_FORTIFY_SOURCE is enabled.

Workaround : Disable CONFIG_FORTIFY_SOURCE in kernel build options.

Details : I am trying to build v5.14.0-rc5 for an old 32 bit arm NAS
system (Cavium CNS3420 based Seagate Central).

The embedded u-boot bootloader on this system is very old and uses
ATAGs to pass parameters to the kernel.

I am confident that the hang problem is occurring because of the
fortified string functions which check the declared size of string
objects before working with them.

My tests show that when booting using kernel v4.19.195 (which does not
have fortified string functions) or with kernel v5.14.0-rc5 with
CONFIG_FORTIFY_SOURCE disabled, that the system does not hang on boot.

Berto Furth (1):
  Make cmdline ATAG work with fortified string fn

 arch/arm/include/uapi/asm/setup.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


base-commit: d6d09a6942050f21b065a134169002b4d6b701ef