linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: fix calling ieee80211_free_txskb with NULL skb
Date: Wed, 19 Feb 2014 13:33:38 +0100	[thread overview]
Message-ID: <1392813218.4733.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1392812916-13656-1-git-send-email-sgruszka@redhat.com> (sfid-20140219_132640_718975_460F3097)

+Emmanuel

Interesting. We just ran into the same issue as well.

> +		struct sk_buff *old_skb = NULL;
> +		unsigned long flags;
>  
>  		ps_dbg(sta->sdata, "STA %pM aid %d: PS buffer for AC %d\n",
>  		       sta->sta.addr, sta->sta.aid, ac);
>  		if (tx->local->total_ps_buffered >= TOTAL_MAX_TX_BUFFER)
>  			purge_old_ps_buffers(tx->local);
>  		if (skb_queue_len(&sta->ps_tx_buf[ac]) >= STA_MAX_TX_BUFFER) {
> -			struct sk_buff *old = skb_dequeue(&sta->ps_tx_buf[ac]);
> +			spin_lock_irqsave(&sta->ps_tx_buf[ac].lock, flags);
> +			/* queue could be modified, recheck length with lock taken */
> +			if (skb_queue_len(&sta->ps_tx_buf[ac]) >= STA_MAX_TX_BUFFER)
> +				old_skb = __skb_dequeue(&sta->ps_tx_buf[ac]);
> +			spin_unlock_irqrestore(&sta->ps_tx_buf[ac].lock, flags);
> +		}
> +		if (old_skb) {

I think that's pointless, you can just say "if (old)" instead as the
dequeue would return NULL.

In any case, while this solves the crash which is a good thing, it still
leaves the code buggy. This crash seems to occur in the following racy
scenario:

 * station is sleeping
 * frame TX to station begins
 * station wakes up
 * frame TX goes into the queue length check, finds long queue
 * pending frames are transmitted
 * queue is now empty
 * old = skb_dequeue() returns NULL
 * *kaboom*

The problem is that you're just fixing the "*kaboom*" part, so the code
will continue like this:

 * old is NULL
 * no kaboom
 * new frame is queued on ps_tx_buf queue
 * frame never gets transmitted

johannes


  parent reply	other threads:[~2014-02-19 12:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 12:28 [PATCH 1/2] mac80211: fix calling ieee80211_free_txskb with NULL skb Stanislaw Gruszka
2014-02-19 12:28 ` [PATCH 2/2] mac80211: protect skb_queue_len(&ps->bc_buf) by lock Stanislaw Gruszka
2014-02-19 13:14   ` Johannes Berg
2014-02-19 13:35     ` Stanislaw Gruszka
2014-02-19 14:51       ` Johannes Berg
2014-02-19 15:09         ` Stanislaw Gruszka
2014-02-19 16:36           ` Johannes Berg
2014-02-20  7:56             ` Stanislaw Gruszka
2014-02-20  7:59               ` Johannes Berg
2014-02-20  8:17               ` Stanislaw Gruszka
2014-02-19 12:33 ` Johannes Berg [this message]
2014-02-19 12:39   ` [PATCH 1/2] mac80211: fix calling ieee80211_free_txskb with NULL skb Grumbach, Emmanuel
2014-02-19 12:46   ` Grumbach, Emmanuel
2014-02-19 13:21   ` Stanislaw Gruszka
2014-02-19 14:48     ` Stanislaw Gruszka
2014-02-19 14:50       ` Johannes Berg
2014-02-19 15:00         ` Stanislaw Gruszka

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=1392813218.4733.20.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).