netdev - Re: bnx2_poll panicking kernel

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: <1215725921.6901.10.camel@dell>
Date:	Thu, 10 Jul 2008 14:38:41 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Josip Rodin" <joy@...uzijast.net>
cc:	"David Miller" <davem@...emloft.net>,
	"billfink@...dspring.com" <billfink@...dspring.com>,
	"bhutchings@...arflare.com" <bhutchings@...arflare.com>,
	netdev <netdev@...r.kernel.org>,
	"mirrors@...ian.org" <mirrors@...ian.org>
Subject: Re: bnx2_poll panicking kernel

On Thu, 2008-07-10 at 14:23 -0700, Josip Rodin wrote:
> I'll try it - but just as I was reading this e-mail, the machine
> managed to
> crash :(
> 
> The log was:
> 
> BUG: unable to handle kernel NULL pointer dereference at
> 00000000000000b8
> IP: [<ffffffff8807ad7e>] :bnx2:bnx2_tx_int+0x7e/0x3f0

This is the same crash that you originally reported.  The driver was
referencing a NULL SKB because the skb_shinfo(skb)->nr_frags was
modified on the previous packet in the TX ring.

If you had applied my debug patch #1 that I posted several weeks ago, it
should have avoided this because we should have saved away the nr_frags
for every packet on the TX ring.


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