public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, "H.J. Lu" <hjl.tools@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg KH <gregkh@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jarkko Sakkinen <jarkko.sakkinen@intel.com>
Subject: Re: Urgent: x86-32 and GNU ld 2.22.52.0.1
Date: Sat, 19 May 2012 12:20:41 +0200	[thread overview]
Message-ID: <20120519102041.GA22271@gmail.com> (raw)
In-Reply-To: <CA+5PVA6n5tJ4tox56ntrJ3T+KgZXnbxpYXjyc5_D9tQ7raQFHw@mail.gmail.com>


* Josh Boyer <jwboyer@gmail.com> wrote:

> On Fri, May 18, 2012 at 12:20 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> > On 05/18/2012 09:14 AM, H.J. Lu wrote:
> >> On Fri, May 18, 2012 at 8:56 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> >>> I need an urgent opinion.  It seems we have an epic mess on our hands.
> >>>
> >>> GNU ld 2.22.52.0.1 silently changed the semantics of section-relative
> >>> symbols that are part of otherwise empty sections, and silently changes
> >>> them to absolute.  We rely on section-relative symbols staying
> >>> section-relative, and actually have several sections in the linker
> >>> script solely for this purpose.
> >>
> >> That is I talked to you a couple days ago:
> >>
> >> http://sourceware.org/bugzilla/show_bug.cgi?id=14052
> >>
> >
> > I know, which was a very good thing... otherwise we'd probably not have
> > tracked this down anywhere near as quickly.  Thank you.
> >
> > The problem is that this version of binutils made it into Fedora 17, and
> > so we now have a large number of users with a known bad binutils in the
> > field...
> 
> We've not seen many kernel bugs that would seem to be blamed 
> on this as of yet.  It does seem like a problem waiting to hit 
> us once F17 goes GA though.  My limited 32-bit F17 machine 
> collection definitely shows the __init_{begin,end} symbols 
> being absolute, but they boot fine.  Likely because the kernel 
> isn't relocated on them.

Relocation is rare, it typically happens with crashdump kernels.

Thanks,

	Ingo

  reply	other threads:[~2012-05-19 10:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 15:56 Urgent: x86-32 and GNU ld 2.22.52.0.1 H. Peter Anvin
2012-05-18 16:11 ` H. Peter Anvin
2012-05-18 16:14 ` H.J. Lu
2012-05-18 16:16   ` H.J. Lu
2012-05-18 16:19     ` H. Peter Anvin
2012-05-18 16:35       ` H.J. Lu
2012-05-18 16:46         ` H. Peter Anvin
2012-05-18 16:50           ` H.J. Lu
2012-05-18 16:51             ` H. Peter Anvin
2012-05-18 18:41               ` Greg KH
2012-05-18 18:52                 ` H. Peter Anvin
2012-05-18 19:11                   ` Greg KH
2012-05-18 19:13                     ` H. Peter Anvin
2012-05-18 16:20   ` H. Peter Anvin
2012-05-18 16:55     ` Josh Boyer
2012-05-19 10:20       ` Ingo Molnar [this message]
2012-05-19 18:12         ` H. Peter Anvin

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=20120519102041.GA22271@gmail.com \
    --to=mingo@kernel.org \
    --cc=gregkh@suse.de \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jarkko.sakkinen@intel.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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