Date: Thu, 27 Sep 2012 12:44:04 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Kim Culhan <w8hdkim@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: ath0_node_lock ath0_com_lock lor Message-ID: <CAJ-Vmo=kVMFJ%2BRBr0EBo=e9TrP97E%2BPovvj9hokzKtAqRRCxnQ@mail.gmail.com> In-Reply-To: <CAKZxVQXCejGG8RZOawdcuyGs3ozhueFQD8U7XFkj5qg7Fwjnog@mail.gmail.com> References: <CAKZxVQXCejGG8RZOawdcuyGs3ozhueFQD8U7XFkj5qg7Fwjnog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <w8hdkim@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=kVMFJ%2BRBr0EBo=e9TrP97E%2BPovvj9hokzKtAqRRCxnQ>