[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1270084631.7101.81.camel@pasglop>
Date: Thu, 01 Apr 2010 12:17:11 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Christoph Lameter <cl@...ux-foundation.org>,
Matthew Wilcox <matthew@....cx>,
Yinghai Lu <yinghai@...nel.org>, Rabin Vincent <rabin@....in>,
lkml <linux-kernel@...r.kernel.org>, penberg@...helsinki.fi,
linux-arch@...r.kernel.org
Subject: Re: start_kernel(): bug: interrupts were enabled early
On Wed, 2010-03-31 at 15:49 -0700, Andrew Morton wrote:
>
> But these things are all utterly gross. The bottom line is that
> radix_tree_init() is manifestly unsuited to being called with local
> interrupts disabled. 773e3eb7b81e5ba13b5155dfb3bb75b8ce37f8f9 was
> just a wrong patch.
Except that powerpc (and now it seems x86) both want to use radix trees
for interrupt handling... At least on powerpc, we trick and use a linear
search until the radix trees are initialized, which we do later during
boot, but that somewhat sucks.
I believe sherry picking things like not calling radix_tree_init() is
going to fix one case today, until we have another one, and another one,
and etc...
I suspect we're better off fixing the root of the problem in down/up.
Cheers,
Ben.
--
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