linux-kernel - Re: [crash] NULL pointer dereference at IP: [<ffffffff812e9ccb>] uart

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]

Date:	Mon, 12 Oct 2009 16:23:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] NULL pointer dereference at IP: [<ffffffff812e9ccb>]
	uart_close+0x2a/0x1e4


* Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > BUG: unable to handle kernel NULL pointer dereference at 0000000000000240
> > IP: [<ffffffff812ea215>] uart_close+0x24/0x1e5
> 
> Very odd indeed. Can you dump the value of
> 
> 	state (ie tty->driver_data)
> 
> 	and if state is non NULL
> 
> 	state->uart_port
> 
> in the crash case
> 
> and if state->uart_port is NULL then there is some head scratching
> required 

Mind sending a debug patch for all info you'd like to see? (The 
advantage of that would be that others who hit this failure can test the 
patch too. Plus it's easier for me to get precisely what you want.)

	Ingo
--
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/