netdev - [PATCH resend 2.6.25 0/12][BNX2X] bugfixes

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>] [day] [month] [year] [list]

Message-ID: <1203935559.8232.204.camel@lb-tlvb-eliezer.il.broadcom.com>
Date:	Mon, 25 Feb 2008 12:32:38 +0200
From:	"Eliezer Tamir" <eliezert@...adcom.com>
To:	davem@...emloft.net, jeff@...zik.org,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: [PATCH resend 2.6.25 0/12][BNX2X] bugfixes

Dave,

Here are just the bug fixes out of the previous update.
Please apply to 2.6.25

1  Spelling fixes

2  Fix bnx2x_init_one() - was printing wrong PCI-E info, failed to release netdev in one case.

3  Link mgmt and BC bugs - many link cfg fixes 
   The move to boot code 4.2.0 is mandatory since it fixes many bugs in the old ones.
   All old devices are being upgraded, all the devices that have been manufactured for a while have the new bootcode.
   (by the time 2.6.25 is out, there should no longer be any devices with pre-4.2.0 bootcode)

4  Correct rx filtering (AKA client-config)

5  Fix stats - rx errors were summed improperly, some were missing.

6  MSI-X / INT#A errata - loading with INT#A after using MSI-X did not work due to a HW bug.

7  HW attention and error handling - many fixes, sometimes improperly acked HW attentions could cause lockup.

8  Fixed slowpath races - fixed up/down racing with timer and fastpath.

9  Tx fixes - fix several bugs in start_xmit (the shiny new rewrite will wait for 2.6.26)

10 Update version

11 Add bnx2x to MAINTAINERS

Thanks
Eliezer

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