The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: ink@jurassic.park.msu.ru, rth@twiddle.net
Cc: akpm@linux-foundation.org, debian-kernel@lists.debian.org,
	linux-kernel@vger.kernel.org
Subject: (fwd) Alpha Linux kernel fails with inconsistent kallsyms data
Date: Fri, 27 Jun 2008 12:07:18 +0200	[thread overview]
Message-ID: <20080627100718.GA19274@stro.at> (raw)

according to the build log
http://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.25-6;arch=alpha;stamp=1214551466
alpha linux image built fine with belows patch,
please have an eye.

thanks

-- 
maks

----- Forwarded message from Bastian Blank <waldi@debian.org> -----

Date: Sun, 22 Jun 2008 22:11:43 +0200
From: Bastian Blank <waldi@debian.org>
To: debian-kernel@lists.debian.org, rth@twiddle.net
Cc: debian-alpha@lists.debian.org
Subject: Alpha Linux kernel fails with inconsistent kallsyms data

Hi folks

The build of the Alpha Linux kernel currently fails[1] with inconsistent
kallsyms data. As I never saw that before, I thought about hardware
problems. But in fact it is a bug in the Linux kernel.

The end of the rodata section is marked with the "__end_rodata" symbol.
This symbol have different aligning constraints than the inittext parts
and therefor the start marked "_sinittext". Because of that the
__end_rodata symbol shifts between < _sinittext and == _sinittext. The
later variant is seen as a code symbol and recorded in the kallsyms
data.

On fix would be to move the exception table a little bit and get some
space between that two areas.

Bastian

[1]: http://buildd.debian.org/fetch.cgi?pkg=linux-2.6&arch=alpha&ver=2.6.25-5&stamp=1213919009&file=log&as=raw

-- 
The face of war has never changed.  Surely it is more logical to heal
than to kill.
		-- Surak of Vulcan, "The Savage Curtain", stardate 5906.5

diff --git a/arch/alpha/kernel/vmlinux.lds.S b/arch/alpha/kernel/vmlinux.lds.S
index f13249b..ef37fc1 100644
--- a/arch/alpha/kernel/vmlinux.lds.S
+++ b/arch/alpha/kernel/vmlinux.lds.S
@@ -25,6 +25,13 @@ SECTIONS
 	} :kernel
 	_etext = .;	/* End of text section */
 
+	NOTES :kernel :note
+	.dummy : {
+		*(.dummy)
+	} :kernel
+
+	RODATA
+
 	/* Exception table */
 	. = ALIGN(16);
 	__ex_table : {
@@ -33,13 +40,6 @@ SECTIONS
 		__stop___ex_table = .;
 	}
 
-	NOTES :kernel :note
-	.dummy : {
-		*(.dummy)
-	} :kernel
-
-	RODATA
-
 	/* Will be freed after init */
 	. = ALIGN(PAGE_SIZE);
 	/* Init code and data */




----- End forwarded message -----

                 reply	other threads:[~2008-06-27 10:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080627100718.GA19274@stro.at \
    --to=max@stro.at \
    --cc=akpm@linux-foundation.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rth@twiddle.net \
    /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