Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Sep 2020 18:42:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        wireless@FreeBSD.org
Subject:   [Bug 249402] Locking issue when requesting an ieee80211 scan
Message-ID:  <bug-249402-21060-n8wt38GgS9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-249402-21060@https.bugs.freebsd.org/bugzilla/>
References:  <bug-249402-21060@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=3D249402

Adrian Chadd <adrian@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adrian@freebsd.org

--- Comment #1 from Adrian Chadd <adrian@freebsd.org> ---
Oh, I'd /totally love/ the comlock to be non-recursive in freebsd. That wou=
ld
force us to tidy up a whole lot of things.

Maybe we should add some _locked() versions that expect the lock held, and =
use
those? I'd like to avoid the unlock/<thing>/relock pattern because it is ra=
cy
as the state can change in that window. (The scan code is notorious for bei=
ng
bad at this..)

--=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-249402-21060-n8wt38GgS9>