From: Johannes Berg <johannes@sipsolutions.net>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cfg80211: initialize rate control after station inserted
Date: Fri, 28 Aug 2009 09:45:57 +0200 [thread overview]
Message-ID: <1251445557.4189.14.camel@johannes.local> (raw)
In-Reply-To: <1251416094-10420-1-git-send-email-reinette.chatre@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
Hi,
Thanks. I'll comment on both patches together. Can you please also tell
us what the problem is this is solving? I'm a bit lost.
I think both of these patches should just rolled into one since this is
also a mac80211 patch -- even if it's for the bit that interacts with
cfg80211.
However, I don't think I actually understand the changes.
> sta_apply_parameters(local, sta, params);
>
> - rate_control_rate_init(sta);
> -
> layer2_update = sdata->vif.type == NL80211_IFTYPE_AP_VLAN ||
> sdata->vif.type == NL80211_IFTYPE_AP;
>
> @@ -742,13 +740,17 @@ static int ieee80211_add_station(struct wiphy *wiphy, struct net_device *dev,
> if (err == -EEXIST && layer2_update) {
> /* Need to update layer 2 devices on reassociation */
> sta = sta_info_get(local, mac);
> - if (sta)
> + if (sta) {
> + rate_control_rate_init(sta);
> ieee80211_send_layer2_update(sta);
> + }
> }
Why is this necessary? It should already have been called for this
station earlier?
> rcu_read_unlock();
> return err;
> }
>
> + rate_control_rate_init(sta);
> +
Also, I don't see anything between the old place that it was called and
the new place you're moving it to that could possibly change the station
parameters?
Same in ibss.c (not quoting it here) where you're only moving it to
after sta_info_insert() -- all that seems to do is add race conditions,
allowing other code to find not-yet-initialised stations.
So the only place I could see a change being necessary would be mlme.c,
but then only moving rate_control_rate_init() to after the flags
settings, not to after the insert.
Am I missing something?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-08-28 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 23:34 [PATCH 1/2] cfg80211: initialize rate control after station inserted Reinette Chatre
2009-08-27 23:34 ` [PATCH 2/2] mac80211: " Reinette Chatre
2009-08-28 7:45 ` Johannes Berg [this message]
2009-08-28 15:45 ` [PATCH 1/2] cfg80211: " reinette chatre
2009-08-28 21:01 ` Johannes Berg
2009-08-28 21:26 ` Luis R. Rodriguez
2009-08-28 21:40 ` Tim Gardner
2009-08-29 5:22 ` Kalle Valo
2009-08-29 9:01 ` Johannes Berg
2009-08-28 22:18 ` reinette chatre
2009-08-29 9:34 ` Johannes Berg
2009-08-31 17:07 ` reinette chatre
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=1251445557.4189.14.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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