netdev - Re: [PATCH 1/1] NET: ipv6, fix potential null dereference

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:	Sun, 10 Jan 2010 12:47:42 +0200
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] NET: ipv6, fix potential null dereference

On Sun, Jan 10, 2010 at 11:38:57AM +0100, Jiri Slaby wrote:
> On 01/10/2010 11:35 AM, Alexey Dobriyan wrote:
> >> Stanse found a potential null dereference
> > 
> > Nobody learns from Coverity, it seems. :^)
> 
> If it is known, why the test is still there?
> 
> I don't have access to the Coverity results anyway.

Well, when Coverity first exposed their database there were innumerable
"potential NULL dereference" defects and people fixed them by moving
stuff and most were bogus and there were flamewars and there were second
wave and so on...

Apparently "check all callers" is very hard to do programmatically.

> > snmp6_unregister_dev() always called with valid idev.

irda patch is not right too: calling tty->ops->hook with NULL tty is
impossible.
--
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