From owner-freebsd-wireless@FreeBSD.ORG Thu Sep 27 19:44:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40896106566B for ; Thu, 27 Sep 2012 19:44:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 13A028FC08 for ; Thu, 27 Sep 2012 19:44:05 +0000 (UTC) Received: by pbbrp8 with SMTP id rp8so4757485pbb.13 for ; Thu, 27 Sep 2012 12:44:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2D9Y6SbfXMoxmzxT0dW/W6eB4MjJdl4Q9v1gYp8vmXs=; b=JWb5ElWUFqUFOLGernXqyWzn2rsa/ahOV4MZ3b2EU5rYEQkZYKZ7CQ89HTk/UF0EXD CuGiHKPMjPoZJZqgh0wGP+l1Q9XWS2RQC53WuW3vg2/fGzIGMYaYGLwmgQeVyp5/AC0i nJ28gH5FndGHny82RN0TU79dEgM61jJVwqXNmM1miOY3bHWsSffi1525sIWj9QACkZpW L5dXIaJe7Y3SFHZ1hcLdbEBh9cKM3vJDDilETeCYeik2bUO90TIl4ZvPrP3iKueo16QY gvqJ++QqZZXF71Is8o8zphmXbfVfp5Ln7qm5iITxpvxPZOo51oZRzijM9nn/cbNyX5Zx /JqQ== MIME-Version: 1.0 Received: by 10.68.189.164 with SMTP id gj4mr14374928pbc.48.1348775044646; Thu, 27 Sep 2012 12:44:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.16.40 with HTTP; Thu, 27 Sep 2012 12:44:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 27 Sep 2012 12:44:04 -0700 X-Google-Sender-Auth: PbWgq1r_e9uaHVbXkz2KYrea-uM Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath0_node_lock ath0_com_lock lor X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2012 19:44:06 -0000 Hm, that's odd. Who wants to go digging to figure out which code paths are causing this? :) I'm knee deep in ANI at the moment. :) Adrian On 26 September 2012 12:49, Kim Culhan wrote: > Have not seen an lor in some time, this noted today fyi > > lock order reversal: > 1st 0xffffff80009267f0 ath0_node_lock (ath0_node_lock) @ > /usr/src/sys/net80211/ieee80211_ioctl.c:1341 > 2nd 0xffffff8000925018 ath0_com_lock (ath0_com_lock) @ > /usr/src/sys/net80211/ieee80211_node.c:2619 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b > kdb_backtrace() at kdb_backtrace+0x39 > witness_checkorder() at witness_checkorder+0xc37 > _mtx_lock_flags() at _mtx_lock_flags+0x83 > ieee80211_node_leave() at ieee80211_node_leave+0x97 > setmlme_common() at setmlme_common+0x3f7 > ieee80211_ioctl_setmlme() at ieee80211_ioctl_setmlme+0x87 > ieee80211_ioctl_set80211() at ieee80211_ioctl_set80211+0x5a5 > in_control() at in_control+0x216 > ifioctl() at ifioctl+0x1020 > kern_ioctl() at kern_ioctl+0x1b0 > sys_ioctl() at sys_ioctl+0x11f > amd64_syscall() at amd64_syscall+0x25a > Xfast_syscall() at Xfast_syscall+0xfb > --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x801203b8a, rsp = > 0x7fffffffd9b8, rbp = 0x7fffffffda20 --- > > > -- > thanks > -kim