[Bug 1192473] New: DE0-Nano-SoC boot fails on 15.3
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473 Bug ID: 1192473 Summary: DE0-Nano-SoC boot fails on 15.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: armv7 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: christian.gross@centerofgravity.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- DE0-Nano-SoC with Leap 15.3 freezes at boot. Booting `openSUSE Leap 15.3' Loading Linux 5.3.18-59.25-default ... Loading initial ramdisk ... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... Deasserting all peripheral resets [freeze] The freeze is caused by the CONFIG_FORTIFY_SOURCE kernel configuration item. The following patch fix the problem. --- /boot/config-5.3.18-59.25-default 2021-09-23 14:34:53.000000000 +0000 +++ .config 2021-07-15 12:07:05.608153308 +0000 @@ -10294,7 +10294,7 @@ CONFIG_LSM_MMAP_MIN_ADDR=0 CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y # CONFIG_HARDENED_USERCOPY is not set -CONFIG_FORTIFY_SOURCE=y +# CONFIG_FORTIFY_SOURCE is not set # CONFIG_STATIC_USERMODEHELPER is not set # CONFIG_HIDDEN_AREA is not set CONFIG_SECURITY_SELINUX=y -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473#c1
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473#c2
Christian Gross
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473
http://bugzilla.opensuse.org/show_bug.cgi?id=1192473#c3
Takashi Iwai
Then it catches it for a long time already. :)
config-5.14.11-2-default:# CONFIG_FORTIFY_SOURCE is not set config-5.3.18-59.25-default:CONFIG_FORTIFY_SOURCE=y config-5.3.18-lp152.92-default:# CONFIG_FORTIFY_SOURCE is not set config-5.3.18-lp152.95-default:# CONFIG_FORTIFY_SOURCE is not set config-5.3.18-lp152.95-mybuild:# CONFIG_FORTIFY_SOURCE is not set
Ah interesting that we forgot to enable it for TW. I'll open another bug report to enable the feature on TW kernel.
It was only set to "y" for the 5.3.18-59.25-default kernel used in 15.3
Yes, that's the new feature on SLE15-SP3 and onward.
However, here is the kernel BUG message:
Loading Linux 5.3.18-59.25-default ... Loading initial ramdisk ... EFI stub: Entering in SVC mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 0.008983] detected buffer overflow in memcpy [ 0.013512] ------------[ cut here ]------------ [ 0.018109] kernel BUG at ../lib/string.c:1090! (snip) [ 0.248691] Backtrace: [ 0.251138] [<c0da914c>] (fortify_panic) from [<c035fd20>] (socfpga_a10_boot_secondary+0x0/0x10c)
So here is the problem. And I guess it's memcpy() call for the trampoline, and possibly the compiler got confused. As a quirk workaround, you may add #define __NO_FORTIFY before the inclusion of header files in arch/arm/mach-socfpga/platsmp.c. Maybe there can be a better way to avoid it, though. Adding Ivan to Cc, as it's about 32bit arm stuff. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com