From: bfgithub@veryspeedy.net
To: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org
Cc: Berto Furth <bfgithub@veryspeedy.net>
Subject: [PATCH v1 0/1] ARM hangs on boot with CONFIG_FORTIFY_SOURCE and ATAGs
Date: Thu, 19 Aug 2021 12:21:44 +1000 [thread overview]
Message-ID: <20210819022144.22719-1-bfgithub@veryspeedy.net> (raw)
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
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-08-19 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 2:21 bfgithub [this message]
2021-08-19 2:21 ` [PATCH v1 1/1] Set cmdline array size to COMMAND_LINE_SIZE bfgithub
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210819022144.22719-1-bfgithub@veryspeedy.net \
--to=bfgithub@veryspeedy.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.