public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"Lu, Hongjiu" <hongjiu.lu@intel.com>,
	"Huang, Ying" <ying.huang@intel.com>
Subject: [BUG]x86: relocatable doesn't work with new binutils
Date: Fri, 17 Dec 2010 10:42:06 +0800	[thread overview]
Message-ID: <1292553726.2323.482.camel@sli10-conroe> (raw)

Hi,
The CONFIG_RELOCATABLE is broken with new binutils, which will make boot
panic. According to Lu Hongjiu, the affected binutils are from
2.20.51.0.12 to 2.21.51.0.3, which are release since Oct 22 this year.
At least ubuntu 10.10 is using such binutils. see:
http://sourceware.org/bugzilla/show_bug.cgi?id=12327
The reason of boot panic is we have 'jiffies = jiffies_64;' in
vmlinux.lds.S. The jiffies isn't in any section. In kernel build, there
is warning saying jiffies is an absolute address and can't be
relocatable. At runtime, jiffies will have virtual address 0.
We can easily workaround this issue by moving jiffies to a section or at
least warn people if such binutils are using. what should we do?

Thanks,
Shaohua


             reply	other threads:[~2010-12-17  2:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17  2:42 Shaohua Li [this message]
2010-12-17  2:59 ` [BUG]x86: relocatable doesn't work with new binutils H. Peter Anvin
2010-12-17  3:21   ` Shaohua Li
2010-12-17  3:24     ` H. Peter Anvin
2010-12-17  4:54       ` Lu, Hongjiu
2010-12-17 10:05     ` Américo Wang
2010-12-17 14:06       ` Shaohua Li

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=1292553726.2323.482.camel@sli10-conroe \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hongjiu.lu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    /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