Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753195Ab0GJT36 (ORCPT ); Sat, 10 Jul 2010 15:29:58 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:58480 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102Ab0GJT34 (ORCPT ); Sat, 10 Jul 2010 15:29:56 -0400 Date: Sat, 10 Jul 2010 12:30:11 -0700 (PDT) Message-Id: <20100710.123011.260095467.davem@davemloft.net> To: eric.dumazet@gmail.com Cc: felipewd@gmail.com, kaber@trash.net, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets From: David Miller In-Reply-To: <1278742649.2538.17.camel@edumazet-laptop> References: <1278695580.2696.55.camel@edumazet-laptop> <1278742649.2538.17.camel@edumazet-laptop> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 748 Lines: 21 From: Eric Dumazet Date: Sat, 10 Jul 2010 08:17:29 +0200 > Strange thing with your crash report is CR2 value, with unexpected value > of 000000000b388000 while RAX value is dce8dce85d415d41 > > Faulting instruction is : > > 48 83 b8 b0 00 00 00 00 cmpq $0x0,0xb0(%rax) > > So I would have expected CR2 being RAX+0xb0, but its not. It could be corruption from elsewhere. Those last four hex digits (0x5d415d41) are "]A]A" in ascii, but that could just be coincidence. -- 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/