Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756933Ab0GMPt7 (ORCPT ); Tue, 13 Jul 2010 11:49:59 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:50339 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753457Ab0GMPt6 (ORCPT ); Tue, 13 Jul 2010 11:49:58 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=f3ne3lgUbUF2K2sgMOzplliPOl1Q1bfXxHp7VvemUqU3Z0LkcLV59r3U7ccGhBSv2p lsoETX+jobSSIbuzJbhajncgR8ME4ogavjINUVWa/9tTMuXm1y2GUIO3THnBFk5AU8eC 3vkQhNlxlPnyNB6CUn6XBbfRzNcJUl/uSYonY= Subject: Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets From: Eric Dumazet To: Felipe W Damasio Cc: Avi Kivity , David Miller , Patrick McHardy , linux-kernel@vger.kernel.org, netdev In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" Date: Tue, 13 Jul 2010 17:49:53 +0200 Message-ID: <1279036193.2634.468.camel@edumazet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1308 Lines: 35 Le mardi 13 juillet 2010 à 11:49 -0300, Felipe W Damasio a écrit : > 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? This is a real bug, but I dont think it can fix your problem. Looking again at your crash, we see RCX=0x720, decimal 1824 As its skb->len, we are freeing an skb that was collapsed or something like that, since 1824 > 1460 (the normal MSS on ethernet) GRO is off on your machine. But coincidently 0x0720 is also a blank char for VGA screen... (0x20 : ASCII space, 0x07 : default attribute) So maybe you hit a corruption outside of network stack. -- 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/