From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [Bugme-new] [Bug 38102] New: BUG kmalloc-2048: Poison overwritten Date: Tue, 05 Jul 2011 06:38:28 +0200 Message-ID: <1309840708.2720.31.camel@edumazet-laptop> References: <20110629145135.5179fb0c.akpm@linux-foundation.org> <1309707971.2523.20.camel@edumazet-laptop> <20110704130531.37cf876e@Nokia-N900> <1309787822.2247.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20110704162726.4072e715@maggie> <20110704164351.338dc12e@maggie> <1309792323.2247.33.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <1309837443.2720.8.camel@edumazet-laptop> <1309839068.2720.15.camel@edumazet-laptop> <1309839258.2720.17.camel@edumazet-laptop> <1309839928.2720.23.camel@edumazet-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Michael =?ISO-8859-1?Q?B=FCsch?= , Andrew Morton , netdev@vger.kernel.org, Gary Zambrano , bugme-daemon@bugzilla.kernel.org, "David S. Miller" , Pekka Pietikainen , Florian Schirmer , Felix Fietkau , Michael Buesch To: Alexey Zaytsev Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:52741 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752326Ab1GEEid (ORCPT ); Tue, 5 Jul 2011 00:38:33 -0400 Received: by wyg8 with SMTP id 8so3732375wyg.19 for ; Mon, 04 Jul 2011 21:38:32 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Le mardi 05 juillet 2011 =C3=A0 08:29 +0400, Alexey Zaytsev a =C3=A9cri= t : > On Tue, Jul 5, 2011 at 08:25, Eric Dumazet w= rote: > > Le mardi 05 juillet 2011 =C3=A0 08:17 +0400, Alexey Zaytsev a =C3=A9= crit : > >> > > >> Check out starting at packet 302893. 383 _identical_ ACKs were sen= t > >> out by the b44 machine within 30 milliseconds. > > > > > > As I said, b44 driver lost at least 200 consecutive frames (source = says > > recovery takes about 20 ms) > > > > TCP then do its normal job. > > >=20 > From my understanding, after a frame is lost, TCP would be waiting fo= r > a retransmit. Or at least, it would not be sending 400 duplicate ACKs > for the single last frame received, right? Let me run tcpdump on the > b44 side now. I'm quite sure I won't see any ACK dups leaving the > stack. Wow, I believe you are on a wrong track. Honestly. Try to unpplug the wire for 100ms, and watch your "duplicate acks disease". Thats exactly what is happening with b44 driver doing a "fast recovery" right now. Thats a moot point. Running tcpdump on your b44 machine will kill your performance even more, it wont solve the b44 bug. If you prefer to 'fix tcp', please open another thread.