| 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
| ||
|
Message-ID: <1203381120.13495.78.camel@dell> Date: Mon, 18 Feb 2008 16:32:00 -0800 From: "Michael Chan" <mchan@...adcom.com> To: "Tony Battersby" <tonyb@...ernetics.com> cc: "Herbert Xu" <herbert@...dor.apana.org.au>, "David Miller" <davem@...emloft.net>, netdev <netdev@...r.kernel.org>, "Greg Kroah-Hartman" <gregkh@...e.de>, linux-kernel@...r.kernel.org Subject: Re: TG3 network data corruption regression 2.6.24/2.6.23.4 On Mon, 2008-02-18 at 17:41 -0500, Tony Battersby wrote: > I am experiencing network data corruption with a 3Com 3C996B-T NIC > (Broadcom NetXtreme BCM5701; driver tg3.ko). I have identified the > following patch as the trigger: Assuming this problem is unique to the 5701, I'm not sure how it is exposed by Herbert's patch. One thing unique on the 5701 is that it double-copies all RX packets so that the data starts at offset 2, but that's quite unrelated to the patch below. > > commit fb93134dfc2a6e6fbedc7c270a31da03fce88db9 > Author: Herbert Xu <herbert@...dor.apana.org.au> > Date: Wed Nov 14 15:45:21 2007 -0800 > > [TCP]: Fix size calculation in sk_stream_alloc_pskb > > > I do not get data corruption when substituting a SysKonnect 9D21 NIC > (which also uses the tg3.ko driver) What Broadcom chip is on the Syskonnect card? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists