All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kees Cook <keescook@chromium.org>
Cc: Alec Ari <neotheuser@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	x86@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] x86/build: Move _etext to actual end of .text
Date: Wed, 5 Jun 2019 20:43:18 +0200	[thread overview]
Message-ID: <20190605184318.GB32750@kroah.com> (raw)
In-Reply-To: <201906051114.6DEF834@keescook>

On Wed, Jun 05, 2019 at 11:16:06AM -0700, Kees Cook wrote:
> On Wed, Jun 05, 2019 at 11:08:13AM -0500, Alec Ari wrote:
> > I'm having this problem too, build is failing:
> > 
> > Invalid absolute R_X86_64_32S relocation: _etext
> > 
> > I stayed on the 4.14 branch to help prevent these kind of breakages,
> > so much for that idea. Gentoo GCC 8.3.0.
> 
> It seems to be a problem with the Gold linker. Using ld.bfd appears to
> work. I haven't narrowed down the problem, unfortunately.
> 
> Greg, given that this change was only for special situations (Clang
> CFI), can you revert this for the stable trees?

Turns out that Android required it to be reverted too, so no one needs
this :(

I'll go revert this, thanks.

greg k-h

  reply	other threads:[~2019-06-05 18:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 16:08 [PATCH] x86/build: Move _etext to actual end of .text Alec Ari
2019-06-05 18:16 ` Kees Cook
2019-06-05 18:43   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-09  9:35 Klaus Kusche
2019-06-09 18:40 ` Johannes Hirte
2019-06-19 18:37   ` Ross Zwisler
2019-06-20 17:58     ` Kees Cook
2019-06-01  8:51 Klaus Kusche
2019-04-23 18:38 Kees Cook
2019-05-14 12:04 ` Johannes Hirte
2019-05-14 15:43   ` Kees Cook
2019-05-14 16:10     ` Johannes Hirte
2019-05-15 18:54       ` Kees Cook
2019-05-16 13:56         ` Johannes Hirte
2019-05-16 17:51           ` Kees Cook

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=20190605184318.GB32750@kroah.com \
    --to=greg@kroah.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neotheuser@gmail.com \
    --cc=stable@vger.kernel.org \
    --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.