Search Linux Wireless

Re: [RFC] mac80211: fix possible tid_rx->reorder_timer use after free

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2012-03-19 at 13:50 +0100, Stanislaw Gruszka wrote:
> Is possible that we arm tid_rx->reorder_timer after del_timer_sync(). To
> fix: first wait for RCU grace period finish and then delete timer. Timer
> will not be armed again as rcu_dereference(sta->ampdu_mlme.tid_rx[tid])
> will return NULL.
> 
> Debug object detected problem with the following warning:
> ODEBUG: free active (active state 0) object type: timer_list hint: sta_rx_agg_reorder_timer_expired+0x0/0xf0 [mac80211]
> 
> Bug report (with full warning):
> https://bugzilla.redhat.com/show_bug.cgi?id=804007
> 
> Reported-by: "jan p. springer" <jsd@xxxxxxxxxx>
> Cc: stable@xxxxxxxxxxxxxxx
> Signed-off-by: Stanislaw Gruszka <sgruszka@xxxxxxxxxx>
> ---
>  net/mac80211/agg-rx.c   |    8 ++++----
>  net/mac80211/sta_info.h |    1 -
>  2 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/net/mac80211/agg-rx.c b/net/mac80211/agg-rx.c
> index 1068f66..2c1223e 100644
> --- a/net/mac80211/agg-rx.c
> +++ b/net/mac80211/agg-rx.c
> @@ -43,10 +43,8 @@
>  #include "ieee80211_i.h"
>  #include "driver-ops.h"
>  
> -static void ieee80211_free_tid_rx(struct rcu_head *h)
> +static void ieee80211_free_tid_rx(struct tid_ampdu_rx *tid_rx)
>  {
> -	struct tid_ampdu_rx *tid_rx =
> -		container_of(h, struct tid_ampdu_rx, rcu_head);
>  	int i;
>  
>  	for (i = 0; i < tid_rx->buf_size; i++)
> @@ -90,10 +88,12 @@ void ___ieee80211_stop_rx_ba_session(struct sta_info *sta, u16 tid,
>  		ieee80211_send_delba(sta->sdata, sta->sta.addr,
>  				     tid, WLAN_BACK_RECIPIENT, reason);
>  
> +	synchronize_rcu();
> +
>  	del_timer_sync(&tid_rx->session_timer);
>  	del_timer_sync(&tid_rx->reorder_timer);
>  
> -	call_rcu(&tid_rx->rcu_head, ieee80211_free_tid_rx);
> +	ieee80211_free_tid_rx(tid_rx);

Hmmm. That synchronize_rcu() could become rather expensive. I've been
trying to reduce our use of synchronize_rcu() now.

I was checking if we could move the timer deletions into
ieee80211_free_tid_rx since call_rcu runs from another softirq, but I'm
not really sure -- the timer softirq could be running on another CPU?

johannes

--
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


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux