Date: Fri, 7 Jun 2013 09:03:57 +0000 (UTC) From: Adrian Chadd <adrian@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r251488 - head/sys/net80211 Message-ID: <201306070903.r5793vj7030951@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: adrian Date: Fri Jun 7 09:03:56 2013 New Revision: 251488 URL: http://svnweb.freebsd.org/changeset/base/251488 Log: Don't hold the node lock over the iterator. The "find node" function call will increase the node reference anyway; so there's no reason to hold the node table lock during the MLME change. The only reason I could think of is to stop overlapping mlme ioctls from causing issues, but this should be fixed a different way. This fixes a whole class of LORs that creep up when nodes are being timed out or removed by hostapd. Tested: * AR5416, hostap, with nodes coming and going. No LORs or stability issues were observed. Modified: head/sys/net80211/ieee80211_ioctl.c Modified: head/sys/net80211/ieee80211_ioctl.c ============================================================================== --- head/sys/net80211/ieee80211_ioctl.c Fri Jun 7 09:02:02 2013 (r251487) +++ head/sys/net80211/ieee80211_ioctl.c Fri Jun 7 09:03:56 2013 (r251488) @@ -1340,12 +1340,17 @@ setmlme_dropsta(struct ieee80211vap *vap if (!IEEE80211_ADDR_EQ(mac, ic->ic_ifp->if_broadcastaddr)) { IEEE80211_NODE_LOCK(nt); ni = ieee80211_find_node_locked(nt, mac); + IEEE80211_NODE_UNLOCK(nt); + /* + * Don't do the node update inside the node + * table lock. This unfortunately causes LORs + * with drivers and their TX paths. + */ if (ni != NULL) { domlme(mlmeop, ni); ieee80211_free_node(ni); } else error = ENOENT; - IEEE80211_NODE_UNLOCK(nt); } else { ieee80211_iterate_nodes(nt, domlme, mlmeop); } @@ -1400,13 +1405,18 @@ setmlme_common(struct ieee80211vap *vap, case IEEE80211_M_MBSS: IEEE80211_NODE_LOCK(nt); ni = ieee80211_find_node_locked(nt, mac); + /* + * Don't do the node update inside the node + * table lock. This unfortunately causes LORs + * with drivers and their TX paths. + */ + IEEE80211_NODE_UNLOCK(nt); if (ni != NULL) { ieee80211_node_leave(ni); ieee80211_free_node(ni); } else { error = ENOENT; } - IEEE80211_NODE_UNLOCK(nt); break; default: error = EINVAL; @@ -1422,6 +1432,12 @@ setmlme_common(struct ieee80211vap *vap, } IEEE80211_NODE_LOCK(nt); ni = ieee80211_find_vap_node_locked(nt, vap, mac); + /* + * Don't do the node update inside the node + * table lock. This unfortunately causes LORs + * with drivers and their TX paths. + */ + IEEE80211_NODE_UNLOCK(nt); if (ni != NULL) { mlmedebug(vap, mac, op, reason); if (op == IEEE80211_MLME_AUTHORIZE) @@ -1431,7 +1447,6 @@ setmlme_common(struct ieee80211vap *vap, ieee80211_free_node(ni); } else error = ENOENT; - IEEE80211_NODE_UNLOCK(nt); break; case IEEE80211_MLME_AUTH: if (vap->iv_opmode != IEEE80211_M_HOSTAP) { @@ -1440,6 +1455,12 @@ setmlme_common(struct ieee80211vap *vap, } IEEE80211_NODE_LOCK(nt); ni = ieee80211_find_vap_node_locked(nt, vap, mac); + /* + * Don't do the node update inside the node + * table lock. This unfortunately causes LORs + * with drivers and their TX paths. + */ + IEEE80211_NODE_UNLOCK(nt); if (ni != NULL) { mlmedebug(vap, mac, op, reason); if (reason == IEEE80211_STATUS_SUCCESS) { @@ -1463,7 +1484,6 @@ setmlme_common(struct ieee80211vap *vap, ieee80211_free_node(ni); } else error = ENOENT; - IEEE80211_NODE_UNLOCK(nt); break; default: error = EINVAL;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201306070903.r5793vj7030951>