All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Arvind Sankar <nivedita@alum.mit.edu>,
	Kees Cook <keescook@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: new build warnings after binutils update
Date: Fri, 14 Aug 2020 12:22:06 +0200	[thread overview]
Message-ID: <20200814102206.GB2367157@gmail.com> (raw)
In-Reply-To: <CAMj1kXGvfjO_e7AgurJ-81o6e4rBC8HkXi3Kkb+ZZfy-MoKcyQ@mail.gmail.com>


* Ard Biesheuvel <ardb@kernel.org> wrote:

> (+ Arvind, Kees)
> 
> On Thu, 13 Aug 2020 at 22:58, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After upgading some software, builds of Linus' tree now produce these warnings:
> >
> > x86_64-linux-gnu-ld: arch/x86/boot/compressed/head_64.o: warning: relocation in read-only section `.head.text'
> > x86_64-linux-gnu-ld: warning: creating DT_TEXTREL in a PIE
> >
> > I upgraded binutils from 2.34-8 to 2.35-1 (Debian versions).
> >
> > $ x86_64-linux-gnu-gcc --version
> > x86_64-linux-gnu-gcc (Debian 9.3.0-13) 9.3.0
> >
> > Any ideas?
> >
> 
> Arvind and I have some patches on the list that fix various relocation
> issues in the decompressor binary.
> 
> As far as I can tell, Arvind's patch to suppress runtime relocations
> [0] addresses this exact issue.
> 
> Unfortunately, in spite of various pings and attempts to get the x86
> maintainers to notice this series, it has been ignored so far. Perhaps
> this is a good time to merge it for -rc1/2?
> 
> [0] https://lore.kernel.org/lkml/20200731202738.2577854-6-nivedita@alum.mit.edu/

It all looked good to me but was a bit late for v5.9, will pick up 
after -rc1.

Thanks,

	Ingo

  reply	other threads:[~2020-08-14 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  4:31 linux-next: new build warnings after binutils update Stephen Rothwell
2020-08-14  7:05 ` Ard Biesheuvel
2020-08-14 10:22   ` Ingo Molnar [this message]
2020-08-14 10:24     ` Ard Biesheuvel
2020-08-14 14:03     ` Sedat Dilek
2020-08-14 19:33     ` Kees Cook
2020-08-15 18:14       ` Ingo Molnar

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=20200814102206.GB2367157@gmail.com \
    --to=mingo@kernel.org \
    --cc=ardb@kernel.org \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nivedita@alum.mit.edu \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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.