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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080721.134608.75595942.davem@davemloft.net>
Date:	Mon, 21 Jul 2008 13:46:08 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Larry.Finger@...inger.net
Cc:	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

From: Larry Finger <Larry.Finger@...inger.net>
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.

Thanks.
--
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/