From owner-freebsd-net@FreeBSD.ORG Wed Nov 14 20:03:36 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA416213 for ; Wed, 14 Nov 2012 20:03:36 +0000 (UTC) (envelope-from rejithomas.d@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9930A8FC12 for ; Wed, 14 Nov 2012 20:03:36 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so1096472vba.13 for ; Wed, 14 Nov 2012 12:03:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=wGF8ogYp0Azt1hMXq8RzrkrO08Avbwwn2AcJNbTz3Y8=; b=KqtQr0LWdUbPsil7xtQ4E2OB1rQZAK69nFlt6D5S7veMj/pb5WqcNQlvzN8tIDRTgX fIywWhLKu4nnMq+5GRRPI/apMnU1R+tyqn3vU051meKu5xKJsKq88G3EyE+UqB0h3cup iHwqq2myiUUnZoN8DPIui/rAnqqi2Qnch5MJjsgLUgQ4L2t2xt7gv/EI54KMi9Sc6bio Nz/lPT9r+XGll8GebvLD62Jeej9Iw2u3OcFhTSFEM+QtfWSIMNcxjamMqWkpOb2u9mjL UgNmgCKfRtCV/LeYcyLu/yhuPmdz5zpqva2Bmj1MVdb4fdD3ZLgF6H2/AH3cB3RLG+Xt LAxQ== MIME-Version: 1.0 Received: by 10.220.227.70 with SMTP id iz6mr12713300vcb.45.1352923415604; Wed, 14 Nov 2012 12:03:35 -0800 (PST) Received: by 10.58.144.196 with HTTP; Wed, 14 Nov 2012 12:03:35 -0800 (PST) Date: Thu, 15 Nov 2012 01:33:35 +0530 Message-ID: Subject: Help wrt LOR in icmp6_rip6_input From: Reji Thomas To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 20:03:37 -0000 Hi, This is regarding a lock order reversal which is already reported in http://ipv4.sources.zabbadoz.net/freebsd/lor/134.html. Pasting the witness backtrace here: lock order reversal 1st 0xc1787144 inp (raw6inp) @ sys/netinet6/icmp6.c:1895 2nd 0xc1788090 inp (rawinp) @ sys/netinet6/icmp6.c:1895 KDB: stack backtrace: kdb_backtrace(c07dcab1,c1788090,c07f043f,c07e928d,c07ec854) at kdb_backtrace+0x2e witness_checkorder(c1788090,9,c07ec854,767,12b) at witness_checkorder+0x6c3 _mtx_lock_flags(c1788090,0,c07ec854,767,c25d5658) at _mtx_lock_flags+0x8a icmp6_rip6_input(cc9fcbec,28,38,1,0) at icmp6_rip6_input+0xb6 icmp6_input(cc9fcc94,cc9fcc34,3a,0,0) at icmp6_input+0xdd4 ip6_input(c25d5600,0,c07e3c86,e8,c08cf944) at ip6_input+0xee7 Is this a valid issue or a spurious one. This seems to be flagged when the icmp6_rip6_input code traverses the pcb list which contains v4 and v6 pcbs. How is the witness lock order established other than the static one ? Is this established on the first locking order encountered (where LOP_NEWORDER flag is passed)?. Regards Reji