> > Sujith Manoharan wrote: > > From: Sujith Manoharan <c_manoha@xxxxxxxxxxxxxxxx> > > > > With drivers that support multi-channel concurrency, make sure that > > the correct context is in use before sending a deauth frame. The > > driver could be in a different context, in which case the frame could > > be dropped. > > The behavior appears to have been changed in: > > commit 8c7d857c4a4a552d8d3e1b2e24e1864ec2989285 > Author: Emmanuel Grumbach <emmanuel.grumbach@xxxxxxxxx> > Date: Wed Jul 25 01:42:36 2012 +0300 > > mac80211: don't call mgd_prepare_tx when associated > > > I am not sure how it can be guaranteed that the driver is on the right context > when trying to send a mgmt frame. > ath9k uses mgd_prepare_tx() to switch to the required context, so I think > this call is necessary even if we are associated. > Why are mgmt frames different from data frames with respect to that? You have a separated queue for mgmt frames that is common to all the contexts? Just like an "offchannel" queue? -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
