netdev - Re: bnx2x null pointer 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]

Message-ID: <1217756201.547.3.camel@lb-tlvb-eliezer>
Date:	Sun, 03 Aug 2008 12:36:41 +0300
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"Bjorn Helgaas" <bjorn.helgaas@...com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Justin Chen" <justin.chen@...com>,
	"Bill Hayes" <bill.hayes@...com>,
	"Myron Stowe" <myron.stowe@...com>
Subject: Re: bnx2x null pointer dereference


On Thu, 2008-07-31 at 15:49 -0700, Bjorn Helgaas wrote:
> The crash below occurred because "params->bp == NULL" in
> bnx2x_update_mng().  This is with the 1.45.11 driver version
> on a RHEL 5.2 kernel.
> 
> This is on a prototype ia64 box, and I'm told that there's
> some bnx2x firmware that is missing from the system firmware,
> so this might be a "we don't care about this problem because
> users will never see this situation" sort of thing.
> 
You are right - the problem is that the data from the board is invalid
since there is no valid boot-code FW burned on it so the board cannot
be used

> But it is annoying that it crashes the box rather than just
> causing the driver to ignore the device.
> 
And this is also true - so we will fix it soon and submit a patch

> Bjorn
> 
Thanks for finding it,
Eilon



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