[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4885DA49.50703@lwfinger.net>
Date: Tue, 22 Jul 2008 08:02:01 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: David Miller <davem@...emloft.net>
CC: kaber@...sh.net, mingo@...e.hu, ischram@...enet.be,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org, j@...fi
Subject: Re: [crash] BUG: unable to handle kernel NULL pointer dereference
at 0000000000000370
David Miller wrote:
> From: Larry Finger <Larry.Finger@...inger.net>
> Date: Tue, 22 Jul 2008 01:34:28 -0500
>
>> David Miller wrote:
>>> From: Larry Finger <Larry.Finger@...inger.net>
>>> Date: Mon, 21 Jul 2008 17:40:10 -0500
>>>
>>>> Sorry :(
>>>>
>>>> I used the davem patch, the second version of your first one, and your second
>>>> one. Both problems persist.
>>>>
>>>> Still plugging away on bisection.
>>> GIT bisecting the lockdep problem is surely going the land you on:
>>>
>>> commit e308a5d806c852f56590ffdd3834d0df0cbed8d7
>> No. It landed on this one.
>
> For the lockdep warnings?
When I was just one commit later, I got both the lockdep warning and the BUG.
This is the commit in question.
commit 16361127ebed0fb8f9d7cc94c6e137eaf710f676
Author: David S. Miller <davem@...emloft.net>
Date: Wed Jul 16 02:23:17 2008 -0700
pkt_sched: dev_init_scheduler() does not need to lock qdisc tree.
We are registering the device, there is no way anyone can get
at this object's qdiscs yet in any meaningful way.
Signed-off-by: David S. Miller <davem@...emloft.net>
Larry
--
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