From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Mike Lothian <mike@fireburn.co.uk>,
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: Wed, 24 Jul 2019 17:57:35 +0200 [thread overview]
Message-ID: <20190724155735.GC5571@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1907241746010.1791@nanos.tec.linutronix.de>
On Wed, Jul 24, 2019 at 05:49:45PM +0200, Thomas Gleixner wrote:
> On Wed, 24 Jul 2019, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 03:44:54PM +0200, Greg KH wrote:
> > > Sorry, I saw that after writing that. You are right, if the others
> > > don't object, that's fine with me. I'll go poke the various build
> > > systems that are failing right now on 5.3-rc1 and try to get them fixed
> > > for this reason.
> >
> > Ok, I dug around and the gold linker is not being used here, only clang
> > to build the source and GNU ld to link, and I am still seeing this
> > error.
>
> Odd combo.
I'm not disagreeing :)
Wait, does clang link things itself and not need ld?
> > Hm, clang 8 does not cause this error, but clang 9 does. Let me go poke
> > the people who are providing this version of clang to see if there's
> > something they can figure out.
>
> Let me try that with my clang variant. Which version of GNU ld are you
> using?
I think it is 2.27:
$ ./ld --version
GNU ld (binutils-2.27-44492f8) 2.27.0.20170315
Which does feel old to me.
I know 2.32 works fine.
Gotta love old tool-chains :(
greg k-h
next prev parent reply other threads:[~2019-07-24 15:57 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 [this message]
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
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=20190724155735.GC5571@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hjl.tools@gmail.com \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mike@fireburn.co.uk \
--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 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.