Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Arvind Sankar <nivedita@alum.mit.edu>
Date:   Fri, 10 Jan 2020 15:50:29 -0500
To:     Borislav Petkov <bp@alien8.de>
Cc:     Arvind Sankar <nivedita@alum.mit.edu>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>, x86@kernel.org,
        linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
        Thomas Lendacky <Thomas.Lendacky@amd.com>
Subject: Re: [PATCH] x86/tools/relocs: Add _etext and __end_of_kernel_reserve
 to S_REL
Message-ID: <20200110205028.GA2012059@rani.riverdale.lan>
References: <20200110202349.1881840-1-nivedita@alum.mit.edu>
 <20200110203828.GK19453@zn.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200110203828.GK19453@zn.tnic>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Jan 10, 2020 at 09:38:28PM +0100, Borislav Petkov wrote:
> On Fri, Jan 10, 2020 at 03:23:49PM -0500, Arvind Sankar wrote:
> > Pre-2.23 binutils makes symbols defined outside sections absolute, so
> > these two symbols break the build on old linkers.
> 
> -ENOTENOUGHINFO
> 
> Which old linkers, how exactly do they break the build, etc etc?
> 
> Please give exact reproduction steps.
> 
> Thx.
> 

binutils-2.21 and -2.22. An x86-64 defconfig will fail with
	Invalid absolute R_X86_64_32S relocation: _etext
and after fixing that one, with
	Invalid absolute R_X86_64_32S relocation: __end_of_kernel_reserve

Similar errors with 32-bit defconfig.

Should I resend with that added to the commit message?