From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe W Damasio Subject: Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets Date: Tue, 13 Jul 2010 11:49:40 -0300 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Avi Kivity , David Miller , Patrick McHardy , linux-kernel@vger.kernel.org, netdev To: Eric Dumazet Return-path: In-Reply-To: <1279032023.2634.384.camel@edumazet-laptop> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi Mr. Dumazet, 2010/7/13 Eric Dumazet : > I currently have no fresh ideas. If you want this problem to be solved, > its important to setup in your lab a workload to trigger again and again > the bug, in order to provide us more crash information. Right. I've been running non-stop since the first bug happened, but so far the problem hasn't surfaced again :-( I've been using the kernel with the patch that you provided me (nf_tproxy.c). Is there a chance that patch fixed the problem? Cheers, Felipe Damasio