Date: Fri, 01 Feb 2019 23:05:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 122033] [ral] [lor] Lock order reversal in ral0 at bootup ieee80211com/ral0 [regression] Message-ID: <bug-122033-227-FEl684uGBy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-122033-227@https.bugs.freebsd.org/bugzilla/> References: <bug-122033-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D122033 Andriy Voskoboinyk <avos@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |avos@freebsd.org Status|Open |Closed --- Comment #3 from Andriy Voskoboinyk <avos@freebsd.org> --- There were few places for com <-> rt2560 LORs. In most cases, the com lock = was obtained before the driver lock; however, there were multiple ieee80211_cancel_scan() calls (from rt2560_start, rt2560_newstate), where t= he driver lock was taken before the call - and that results in LOR because ieee80211_cancel_scan() takes com lock inside. The issue was fixed in base r178354 - cancel_scan() calls from rt2560_start were dropped and rt2560_newstate is now called under com lock (and never ca= lled directly from the driver code). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-122033-227-FEl684uGBy>