From: Mike Lothian <mike@fireburn.co.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
bhe@redhat.com, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
lijiang@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be reserved
Date: Tue, 20 Aug 2019 13:46:45 +0100 [thread overview]
Message-ID: <CAHbf0-E5S+Pc4Q5gk-=sZfygMWyjkXBLxUg3TXm=+qwP8fES=A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1908191530560.2147@nanos.tec.linutronix.de>
I've updated the bug some more with more info
I can't replicate this on RHEL7 with GCC 4.8.5 or GCC 7.3.1
My GCC is as follows:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-9.2.0/work/gcc-9.2.0/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/9.2.0
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/python
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls
--without-included-gettext --enable-checking=release
--with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 9.2.0
p1' --disable-esp --enable-libstdcxx-time --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--enable-multilib --with-multilib-list=m32,m64 --disable-altivec
--disable-fixed-point --enable-targets=all --enable-libgomp
--disable-libmudflap --disable-libssp --disable-systemtap
--enable-vtable-verify --enable-lto --with-isl
--disable-isl-version-check --enable-default-pie --enable-default-ssp
Thread model: posix
gcc version 9.2.0 (Gentoo 9.2.0 p1)
Could this be related to the --enable-default-ssp or --enable-default-pie?
On Mon, 19 Aug 2019 at 14:31, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Mon, 19 Aug 2019, Mike Lothian wrote:
> >
> > I'm using GCC 9.2, binutils 2.32. I used to use the gold linker but
> > I've just switched back to using ld.bfd based on this discussion
> >
> > My .config can be found at:
> > https://raw.githubusercontent.com/FireBurn/KernelStuff/master/dot_config_tip
>
> Does this combo successfully build 5.2 or is this a general problem?
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2019-08-20 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 18:40 [PATCH v3 0/2] x86: SME: Kexec/kdump memory loading fix Lendacky, Thomas
2019-06-19 18:40 ` [PATCH v3 1/2] x86/mm: Identify the end of the kernel area to be reserved Lendacky, Thomas
2019-06-20 9:58 ` [tip:x86/kdump] " tip-bot for Thomas Lendacky
2019-07-13 14:59 ` [PATCH v3 1/2] " Mike Lothian
2019-07-14 10:16 ` Thomas Gleixner
2019-07-14 10:27 ` Mike Lothian
2019-07-15 8:12 ` Thomas Gleixner
[not found] ` <CAHbf0-F9yUDJ=DKug+MZqsjW+zPgwWaLUC40BLOsr5+t4kYOLQ@mail.gmail.com>
2019-07-15 9:25 ` Thomas Gleixner
2019-07-15 10:35 ` Thomas Gleixner
2019-07-15 20:16 ` H.J. Lu
2019-07-23 13:05 ` Greg KH
2019-07-23 13:31 ` Thomas Gleixner
2019-07-23 13:44 ` Greg KH
2019-07-24 15:34 ` Greg KH
2019-07-24 15:49 ` Thomas Gleixner
2019-07-24 15:57 ` Greg KH
2019-07-24 16:03 ` Thomas Gleixner
2019-07-24 16:16 ` Greg KH
2019-07-24 20:02 ` Thomas Gleixner
2019-07-24 20:20 ` Thomas Gleixner
2019-07-25 6:24 ` Greg KH
2019-08-14 11:09 ` Mike Lothian
2019-08-19 12:53 ` Mike Lothian
2019-08-19 13:08 ` Thomas Gleixner
2019-08-19 13:21 ` Mike Lothian
2019-08-19 13:31 ` Thomas Gleixner
2019-08-20 12:46 ` Mike Lothian [this message]
2019-07-24 16:22 ` Peter Zijlstra
2019-07-24 16:01 ` Thomas Gleixner
2019-07-23 13:43 ` Greg KH
2019-06-19 18:40 ` [PATCH v3 2/2] x86/mm: Create a workarea in the kernel for SME early encryption Lendacky, Thomas
2019-06-20 9:58 ` [tip:x86/kdump] " tip-bot for Thomas Lendacky
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='CAHbf0-E5S+Pc4Q5gk-=sZfygMWyjkXBLxUg3TXm=+qwP8fES=A@mail.gmail.com' \
--to=mike@fireburn.co.uk \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).