netdev - Re: [PATCH 1/1] tg3: Avoid Send BD corruption

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080911165913.GA27725@xw6200.broadcom.net>
Date:	Thu, 11 Sep 2008 09:59:13 -0700
From:	"Matt Carlson" <mcarlson@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	"Matthew Carlson" <mcarlson@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Michael Chan" <mchan@...adcom.com>,
	"andy@...yhouse.net" <andy@...yhouse.net>
Subject: Re: [PATCH 1/1] tg3: Avoid Send BD corruption

On Wed, Sep 10, 2008 at 10:46:18PM -0700, David Miller wrote:
> From: "Matt Carlson" <mcarlson@...adcom.com>
> Date: Wed, 10 Sep 2008 22:12:45 -0700
> 
> > On 5761 and 5784 ASIC revision chips, there is a chance that send BDs
> > can be corrupted when CLKREQ is enabled.  This patch turns CLKREQ off
> > while the driver is in control of the device.
> >
> > This patch also bumps up the version to 3.95.
> >
> > Signed-off-by: Matt Carlson <mcarlson@...adcom.com>
> > Signed-off-by: Michael Chan <mchan@...adcom.com>
> 
> Are users really hitting this or was this discovered by your own
> internal testing and verification?

The bug was discovered by our own internal testing, but this bug is
severe enough to warrant submission to the net-2.6 kernel.  I'll be
sending a patch to stable as well.

These chips are relatively new so there isn't a whole lot of opportunity
for users to experience the problem yet.  As the chips are distributed,
the likelyhood that users will encounter this problem is pretty high.


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