Message ID | 20160713115758.25395-1-yanivma@ti.com (mailing list archive) |
---|---|
State | Superseded |
Delegated to: | Johannes Berg |
Headers | show |
On Wed, 2016-07-13 at 14:57 +0300, Yaniv Machani wrote: > From: Meirav Kama <meiravk@ti.com> > > Upon forwarding frames from Rx to Tx in mesh, driver clones the skb. > It zeros the tx_info and doesn't set hw_queue correctly. It then > enqueues > the frame in queue 0 (VOICE) instead of the correct queue. > Upon re-queue of this frame, driver inserts it to the correct queue > (e.g. BE). > After that, driver dequeue frames from 2 different queues and sends > them out of order. > To fix this, driver will set the tx_info->hw_queue to the correct > queue when cloning the skb. > Makes sense, but the subject is a bit misleading - can you come up with a better one? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/net/mac80211/rx.c b/net/mac80211/rx.c index 9a1eb70..88dc744 100644 --- a/net/mac80211/rx.c +++ b/net/mac80211/rx.c @@ -2392,6 +2392,7 @@ ieee80211_rx_h_mesh_fwding(struct ieee80211_rx_data *rx) info->flags |= IEEE80211_TX_INTFL_NEED_TXPROCESSING; info->control.vif = &rx->sdata->vif; info->control.jiffies = jiffies; + info->hw_queue = q; if (is_multicast_ether_addr(fwd_hdr->addr1)) { IEEE80211_IFSTA_MESH_CTR_INC(ifmsh, fwded_mcast); memcpy(fwd_hdr->addr2, sdata->vif.addr, ETH_ALEN);