netdev - Re: tty_register_device NULL pointer dereference in 2.6.31-rc4

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: <20090725131046.0f076f37@lxorguk.ukuu.org.uk>
Date:	Sat, 25 Jul 2009 13:10:46 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Oliver Hartkopp <oliver@...tkopp.net>,
	Linux Netdev List <netdev@...r.kernel.org>,
	linux-bluetooth@...r.kernel.org
Subject: Re: tty_register_device NULL pointer dereference in 2.6.31-rc4

> > tty_register_device appears to have been called with a NULL pointer. Not
> > sure why however.
> 
> if that is the pointer for the struct device, then that used to be fine
> in the past. Not all RFCOMM device have a parent when they are created.

The tty layer doesn't care about the struct device really. Nothing there
has changed. The NULL passed appears to be the driver argument.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html