Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@web.de>
Cc: wireless <linux-wireless@vger.kernel.org>,
	andrey@cozybit.com, John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: initialize RC data for all mesh links upon allocation
Date: Mon, 29 Dec 2008 12:14:51 +0100	[thread overview]
Message-ID: <1230549291.3116.27.camel@johannes> (raw)
In-Reply-To: <200812272219.49555.chunkeey@web.de>

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

On Sat, 2008-12-27 at 22:19 +0100, Christian Lamparter wrote:
> This patch fixes a panic that might occur, if the device is part of a mesh
> and tries to send with a higher rate index than "0".

I think we really should try to move this into sta_info_alloc() at some
point ...

> kernel BUG at net/mac80211/rate.c:239! 
> invalid opcode: 0000 [#1] SMP 
> [...]
>  Call Trace:
>  <IRQ> <0> ? invoke_tx_handlers+0x474/0xb57 [mac80211]
>  ? __ieee80211_tx_prepare+0x260/0x2a8 [mac80211]
>  ? ieee80211_master_start_xmit+0x300/0x43a [mac80211]
>  ? __qdisc_run+0xde/0x1da
>  ? net_tx_action+0xb4/0x102
>  Kernel panic - not syncing: Fatal exception in interrupt
> 
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> I'm not sure if we need a rate_control_rate_init in mesh_neighbour_update as well.
> So, there's one patch[1] with and another one[2] without rate_control_rate_init in
> mesh_neighbour_update...

Hard to tell.

> ---
> diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c
> index faac101..1c1474d 100644
> --- a/net/mac80211/mesh_plink.c
> +++ b/net/mac80211/mesh_plink.c
> @@ -107,6 +107,7 @@ static struct sta_info *mesh_plink_alloc(struct ieee80211_sub_if_data *sdata,
>  
>  	sta->flags = WLAN_STA_AUTHORIZED;
>  	sta->sta.supp_rates[local->hw.conf.channel->band] = rates;
> +	rate_control_rate_init(sta);
>  
>  	return sta;
>  }
> @@ -244,6 +245,7 @@ void mesh_neighbour_update(u8 *hw_addr, u64 rates, struct ieee80211_sub_if_data
>  
>  	sta->last_rx = jiffies;
>  	sta->sta.supp_rates[local->hw.conf.channel->band] = rates;
> +	rate_control_rate_init(sta);
>  	if (peer_accepting_plinks && sta->plink_state == PLINK_LISTEN &&
>  			sdata->u.mesh.accepting_plinks &&
>  			sdata->u.mesh.mshcfg.auto_open_plinks)
> ---
> diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c
> index faac101..a540ab8 100644
> --- a/net/mac80211/mesh_plink.c
> +++ b/net/mac80211/mesh_plink.c
> @@ -107,6 +107,7 @@ static struct sta_info *mesh_plink_alloc(struct ieee80211_sub_if_data *sdata,
>  
>  	sta->flags = WLAN_STA_AUTHORIZED;
>  	sta->sta.supp_rates[local->hw.conf.channel->band] = rates;
> +	rate_control_rate_init(sta);
>  
>  	return sta;
>  }
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-12-29 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27 21:19 [PATCH] mac80211: initialize RC data for all mesh links upon allocation Christian Lamparter
2008-12-29 11:14 ` Johannes Berg [this message]

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=1230549291.3116.27.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=andrey@cozybit.com \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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