[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1219933410.7107.296.camel@pmac.infradead.org>
Date: Thu, 28 Aug 2008 14:23:30 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Arjan van de Ven <arjan@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
linuxppc-dev@...abs.org, linux-next@...r.kernel.org, mingo@...e.hu
Subject: Re: [BUG] linux-next: Tree for August 26 - Badness at
kernel/notifier.c:25
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@...b.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?
$ egrep _[es]init\|_[es]text\|isa_bridge_notify System.map
c000000000000000 T _stext
c00000000045d000 T _etext
c000000000463ca8 t .isa_bridge_notify
c00000000063a000 T _sinittext
c00000000067c3bc T _einittext
c00000000071fd80 d isa_bridge_notify
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@...el.com Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists