linux-kernel - Re: x86/purgatory: undefined symbol __stack_chk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190928124129.GA97534@gmail.com>
Date:   Sat, 28 Sep 2019 14:41:29 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Andreas Smas <andreas@...elycoder.com>,
        linux-kernel@...r.kernel.org, X86 ML <x86@...nel.org>
Subject: Re: x86/purgatory: undefined symbol __stack_chk_fail


* Randy Dunlap <rdunlap@...radead.org> wrote:

> On 9/3/19 8:50 AM, Andreas Smas wrote:
> > Hi,
> > 
> > For me, kernels built including this commit
> > b059f801a937 (x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS)
> > 
> > results in kexec() failing to load the kernel:
> > 
> > kexec: Undefined symbol: __stack_chk_fail
> > kexec-bzImage64: Loading purgatory failed
> > 
> > Can be seen:
> > 
> > $ readelf -a arch/x86/purgatory/purgatory.ro | grep UND
> >      0: 0000000000000000     0 NOTYPE  LOCAL  DEFAULT  UND
> >     51: 0000000000000000     0 NOTYPE  GLOBAL DEFAULT  UND __stack_chk_fail
> > 
> > Using: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
> > 
> > Adding -ffreestanding or -fno-stack-protector to ccflags-y in
> > arch/x86/purgatory/Makefile
> > fixes the problem. Not sure which would be preferred.
> > 
> 
> Hi,
> Do you have a kernel .config file that causes this?
> I can't seem to reproduce it.

Does it go away with this fix in x86/urgent:

  ca14c996afe7: ("x86/purgatory: Disable the stackleak GCC plugin for the purgatory")

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent

?

Thanks,

	Ingo