From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: IPV6 possible recursive locking Date: Fri, 04 Aug 2006 17:56:27 -0700 Message-ID: <44D3ECBB.6060901@linux.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Petr Vandrovec , netdev@vger.kernel.org, mingo@elte.hu, davem@davemloft.net Return-path: Received: from mga09.intel.com ([134.134.136.24]:30469 "EHLO orsmga102-1.jf.intel.com") by vger.kernel.org with ESMTP id S1422686AbWHEA7e (ORCPT ); Fri, 4 Aug 2006 20:59:34 -0400 To: Herbert Xu In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Herbert Xu wrote: >> [] sk_clone+0xd4/0x350 >> [] inet_csk_clone+0x11/0x70 >> [] tcp_create_openreq_child+0x24/0x480 >> [] tcp_v6_syn_recv_sock+0x2c2/0x6f0 >> [] tcp_check_req+0x229/0x3a0 >> [] tcp_v6_do_rcv+0x17d/0x400 >> [] tcp_v6_rcv+0x7e5/0x850 > > Yes this is a known problem. The lock validator needs to learn how > to distinguish between parent and child sockets. Hmm I remember fixing sk_clone before.. or was that skb_clone, I'd have ot check. Anyway I'll check this out either later today or tomorrow in more detail and will send a patch.