From: Milton Miller <miltonm@bga•com>
To: David Woodhouse <dwmw2@infradead•org>
Cc: LKML <linux-kernel@vger•kernel.org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
linuxppc-dev@ozlabs•org, linux-next@vger•kernel.org,
mingo@elte•hu, Arjan van de Ven <arjan@linux•intel.com>
Subject: Re: [BUG] linux-next: Tree for August 26 - Badness at kernel/notifier.c:25
Date: Thu, 28 Aug 2008 12:14:39 -0500 (CDT) [thread overview]
Message-ID: <200808281714.m7SHEdCX096569@sullivan.realtime.net> (raw)
In-Reply-To: <1219935307.7107.302.camel@pmac.infradead.org>
David Woodhouse dwmw2 at infradead.org
Fri Aug 29 00:55:07 EST 2008
> On Thu, 2008-08-28 at 15:23 +0100, David Woodhouse wrote:
>> On Thu, 2008-08-28 at 00:38 +1000, Stephen Rothwell wrote:
>>> Hi Arjan,
>>>
>>> On Thu, 28 Aug 2008 00:33:08 +1000 Stephen Rothwell <sfr at canb.auug.org.au> wrote:
>>>>
>>>> The original reported trace was during setup_system which is very early in
>>>> the boot.
>>>
>>> But, of course, that version didn't have the necessary extra dereference
>>> of the function address ...
>>>
>>> And the later debug patch did not check the address at register time,
>>> only at notify time.
>>>
>>> The later trace also looks to be early in the boot.
>>
>> It's isa_bridge_notify(), which is neither within _[se]text nor
>> _[se]inittext, so the core_kernel_text() function disavows it.
>>
>> Where are __devinit functions supposed to end up?
>
> The TEXT_TEXT macro defined in <asm-generic/vmlinux.lds.h> should get
> this right... but we don't use it. Is there any particular reason for
> that, or should we....
gitk -- arch/powerpc/kernel/vmlinux.S
e95c91821fa56b489d7beb74103a419466c5ec10
[POWERPC] Fix link errors for allyesconfig
An allyesconfig build creates a .text section that is so big that the
.text.init.refok and .fixup sections are too far away for the relocations
to be fixed up correctly. This patch fixes that by linking all the
relevent text sections for each file together.
Suggested by Paul Mackerras.
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Paul Mackerras <paulus@samba•org>
Although I think its really fac23fe4be23259a8eaa9bad822f5b14dd07d15c
powerpc: Introduce infrastructure for feature sections with alternatives
that causes the problems.
If the problem is only reaching the branch-out-of-fixup-section, then
we could create a macro that caculates the branch as if it were already
at the destination address (using something like
b (target-fixup_start)-(current-alternative_start)
and then removing the code that determines the branch target goes beyond
the feature section.
Just a concept, have't tried it yet and don't know if there are other
problems with .text.init.refok.
Or we fix our defintion and put a comment next to TEXT_TEXT that we
don't use it for future editors.
>
> Signed-off-by: David Woodhouse <David.Woodhouse at intel.com>
>
> --- linux-2.6.26.ppc64/arch/powerpc/kernel/vmlinux.lds.S~ 2008-07-13 22:51:29.000000000 +0100
> +++ linux-2.6.26.ppc64/arch/powerpc/kernel/vmlinux.lds.S 2008-08-28 15:39:14.000000000 +0100
> @@ -35,10 +35,11 @@ SECTIONS
> ALIGN_FUNCTION();
> *(.text.head)
> _text = .;
> - *(.text .fixup .text.init.refok .exit.text.refok)
> + TEXT_TEXT
> SCHED_TEXT
> LOCK_TEXT
> KPROBES_TEXT
> + *(.fixup)
>
> #ifdef CONFIG_PPC32
> *(.got1)
>
> --
> David Woodhouse Open Source Technology Centre
> David.Woodhouse at intel.com Intel Corporation
next prev parent reply other threads:[~2008-08-28 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 8:40 linux-next: Tree for August 26 Stephen Rothwell
2008-08-26 18:27 ` [BUG] linux-next: Tree for August 26 - Badness at kernel/notifier.c:25 Kamalesh Babulal
2008-08-26 20:22 ` Arjan van de Ven
2008-08-27 11:12 ` Kamalesh Babulal
2008-08-27 13:48 ` Arjan van de Ven
2008-08-27 14:33 ` Stephen Rothwell
2008-08-27 14:38 ` Stephen Rothwell
2008-08-28 14:23 ` David Woodhouse
2008-08-28 14:55 ` David Woodhouse
2008-08-28 17:14 ` Milton Miller [this message]
2008-08-27 17:52 ` Kamalesh Babulal
2008-08-26 23:49 ` [PATCH -next] net: fix compilation NG when !CONFIG_MODULE Hiroshi Shimamoto
2008-08-26 23:56 ` [PATCH -next] initramfs: fix compilation warning Hiroshi Shimamoto
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=200808281714.m7SHEdCX096569@sullivan.realtime.net \
--to=miltonm@bga$(echo .)com \
--cc=arjan@linux$(echo .)intel.com \
--cc=dwmw2@infradead$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mingo@elte$(echo .)hu \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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