Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752718Ab0GNDvg (ORCPT ); Tue, 13 Jul 2010 23:51:36 -0400 Received: from mail-vw0-f46.google.com ([209.85.212.46]:39093 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751121Ab0GNDvf (ORCPT ); Tue, 13 Jul 2010 23:51:35 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=l47BRQthb/L6ItlD1WA4zsxPsXvYLaMT18SwM87Ix+3QFAfhsj9ZshUSH5/r414pcr goq9Ibk6aqfu0LAFiQjZdRtAxpdOiJtmLz98u8glkpj7j6haHT/JvxTcAaWyihevjqmV yvejlmWxsswTBlOoeC45n2/nvfrMBCeC10hwo= MIME-Version: 1.0 In-Reply-To: <1279078985.2444.105.camel@edumazet-laptop> References: <1278626921.2435.73.camel@edumazet-laptop> <1278695580.2696.55.camel@edumazet-laptop> <1278742649.2538.17.camel@edumazet-laptop> <4C395459.6080407@redhat.com> <1278835332.2538.51.camel@edumazet-laptop> <1279032023.2634.384.camel@edumazet-laptop> <1279036193.2634.468.camel@edumazet-laptop> <1279077678.2444.95.camel@edumazet-laptop> <1279078985.2444.105.camel@edumazet-laptop> Date: Wed, 14 Jul 2010 00:51:33 -0300 Message-ID: Subject: Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets From: Felipe W Damasio To: Eric Dumazet Cc: Avi Kivity , David Miller , Patrick McHardy , linux-kernel@vger.kernel.org, netdev Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1361 Lines: 39 Hi, 2010/7/14 Eric Dumazet : >> I can, but my bosses will kick my ass if I bring down the ISP again :) > > I have no guarantee at all, even if we find the bug. Ok :-) >> If you think it's the only way to find the problem I'll tell them that >> I need to do it. In this case, please tell me what other config >> options/tools I can use to get as much info as possible...since I'll >> probably be able to test this only once more on the production >> environment for debugging purposes. > > You really should try to setup a lab to trigger the bug, and not doing > experiments on production :) Right, I'm trying. The thing is: The ISP is a 200Mbps network with 10,000 users. The first time it took around 2 minutes to trigger the bug. The second time it took around 17 minutes. So I *think* it's some TCP flag with some weird content...but I can't find out what it is so I can trigger it on the lab. So my only guess is to enable every possible debug flag I can think of to track the bug down on the production environment. Any hints here would be appreciated :) Cheers, Felipe Damasio -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/