Search Linux Wireless

Re: [crash] BUG: unable to handle kernel NULL pointer dereference at 0000000000000370

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David Miller wrote:
From: Patrick McHardy <kaber@xxxxxxxxx>
Date: Mon, 21 Jul 2008 22:51:53 +0200

David Miller wrote:
From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
Date: Mon, 21 Jul 2008 15:38:47 -0500

David Miller wrote:
No further backtrace?  That will tell us what driver is causing
this.
Yes, I have a full backtrace.

It starts with possible recursive locking in NetworkManager, and goes directly into the Warning - this came from a later pull of Linus's tree.
That helps a lot, I'm looking at this now.
I'm guessing this needs similar lockdep class initializations
to _xmit_lock since it essentially has the same nesting rules.

Yes, I figured that out just now :-)

Maybe something like the following should do it?


It looks correct in any case. I'm not sure whether it fixes
this lockdep warning though, according to the backtrace and
module list its b43 and dev_mc_sync in net/mac80211/main.c
that are causing the error, which don't seem to be included
in your patch. I'm unable to find where it previously
initialized the xmit_lock lockdep class though, so I must
be missing something :)


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux