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]

Date:	Mon, 16 Jun 2008 08:52:13 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Ben Hutchings" <bhutchings@...arflare.com>,
	"Josip Rodin" <joy@...uzijast.net>
cc:	netdev@...r.kernel.org, mirrors@...ian.org
Subject: Re: bnx2_poll panicking kernel

Ben Hutchings wrote:

> Josip Rodin wrote:
> > Hi,
> > 
> > Has anyone seen the below bug before? I'm already upgrading 
> in hope that it
> > might be already fixed in a newer kernel, but anyway.
> > 
> > It started happening a few days ago, on a load of a few 
> tens of MB/s (Debian
> > rsync mirroring). It doesn't happen on every mirror pulse, 
> so it's not
> > exactly reproducible...
> 
> That might be a result of the bug fixed by this commit, which would be
> triggered by heavy traffic:
> 
> commit 6f535763165331bb91277d7519b507fed22034e5
> Author: David S. Miller <davem@...set.davemloft.net>
> Date:   Thu Oct 11 18:08:29 2007 -0700
> 
>     [NET]: Fix NAPI completion handling in some drivers.
> 

This commit fixed a bug that existed for a very short time after
the patch to make the NAPI struct independent of the netdevice was
committed.

So I think it is unlikely that Josip's panic is caused by this.

Josip, please provide more information such as driver version from
ethtool -i, lspci, which version did you first see the problem, and
whether the latest in 2.6.25 has the same problem.  Thanks.

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