ath0_node_lock ath0_com_lock lor

[Adrian Chadd]

On 28 September 2012 07:03, PseudoCylon <moonlightakkiy at yahoo.ca> wrote:

>> Hm, that's odd. Who wants to go digging to figure out which code paths
>> are causing this? :)

> A suggestion
>
> in setmlme_dropsta()
> http://fxr.watson.org/fxr/source/net80211/ieee80211_ioctl.c#L1331
>
> Just forget about node lock and call ieee80211_find_node() instead of
> ieee80211_find_node_locked(). (I believe this lor occurs only in AP
> mode.)

Right, it's in the wiki, but I don't know what the two code paths are
that have inverted locks.

So would someone please map out the two code paths and where the locks
are grabbed, so I/we can think about how this should be better fixed?

Thanks,




Adrian