On Wed, 2011-12-07 at 19:12 +0530, Vasanthakumar Thiagarajan wrote:
> /**
> + * cfg80211_roamed_bss - notify cfg80211 of roaming
> + *
> + * @dev: network device
> + * @bss: entry of bss to which STA got roamed (may be %NULL)
I think you should check that it isn't, that's an implementation thing
of __cfg80211_roamed() I think? Semantically, I don't think this should
happen here?
It would also be good to note that the reference to the bss is given to
the function and it will be released by it.
> +void cfg80211_roamed_bss(struct net_device *dev, struct cfg80211_bss *bss,
> + struct ieee80211_channel *channel,
> + const u8 *bssid, const u8 *req_ie, size_t req_ie_len,
> + const u8 *resp_ie, size_t resp_ie_len, gfp_t gfp)
> +{
> struct wireless_dev *wdev = dev->ieee80211_ptr;
> struct cfg80211_registered_device *rdev = wiphy_to_dev(wdev->wiphy);
> struct cfg80211_event *ev;
Hmm, now that I think about it more, I think the calling convention is
really strange. Why pass the channel and bssid when the BSS struct is
already known?
Why not make cfg80211_roamed() do the BSS lookup (which would also
reduce the race for drivers that don't use _bss()) based on the info,
and then call a cfg80211_roamed_bss() that doesn't get channel/bssid.
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
