Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: "Grumbach\, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] mac80211: Call mgd_prepare_tx before deauthentication
Date: Wed, 17 Sep 2014 11:47:33 +0530	[thread overview]
Message-ID: <21529.10109.308613.563543@gargle.gargle.HOWL> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB31B52311D@hasmsx107.ger.corp.intel.com>

Grumbach, Emmanuel wrote:
> It can wait until a context switch will occur in ath9k - you should switch
> from time to time anyway to avoid starvation, and this is not under the radar
> of mac80211.

But mac80211 doesn't wait for a switch to happen. It removes the BSS and station
info immediately after sending the deauth frame to the driver and the driver doesn't
get a chance to process the pending frames for the other context. I think
this race could be avoided by making sure the driver switches to the
required context before sending deauth.

Sujith



  reply	other threads:[~2014-09-17  6:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  4:33 [PATCH] mac80211: Call mgd_prepare_tx before deauthentication Sujith Manoharan
2014-09-17  4:54 ` Sujith Manoharan
2014-09-17  5:01   ` Grumbach, Emmanuel
2014-09-17  5:44     ` Sujith Manoharan
2014-09-17  5:50       ` Grumbach, Emmanuel
2014-09-17  6:01         ` Sujith Manoharan
2014-09-17  6:04           ` Grumbach, Emmanuel
2014-09-17  6:17             ` Sujith Manoharan [this message]
2014-09-17 19:01               ` Emmanuel Grumbach
2014-09-18  3:05                 ` Sujith Manoharan
2014-09-18  4:13                   ` Sujith Manoharan
2014-09-18  5:08                     ` Emmanuel Grumbach
2014-09-18  5:49                       ` Sujith Manoharan
2014-10-09  9:40                         ` Johannes Berg
2014-10-09 10:22                           ` Sujith Manoharan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21529.10109.308613.563543@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox