Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: linux-wireless@vger.kernel.org, reinette.chatre@intel.com
Subject: Re: [RFC PATCHv2] mac80211: Fix circular locking dependency in ARP filter handling
Date: Tue, 08 Jun 2010 10:03:56 +0200	[thread overview]
Message-ID: <1275984236.3706.45.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1275978299-18237-1-git-send-email-juuso.oikarinen@nokia.com>

On Tue, 2010-06-08 at 09:24 +0300, Juuso Oikarinen wrote:

> @@ -161,10 +161,20 @@ enum ieee80211_bss_change {
>  	BSS_CHANGED_BEACON_ENABLED	= 1<<9,
>  	BSS_CHANGED_CQM			= 1<<10,
>  	BSS_CHANGED_IBSS		= 1<<11,
> +#ifdef CONFIG_INET
> +	BSS_CHANGED_ARP_ADDR_LIST	= 1<<12,
> +#endif

Ick, don't do that, all drivers would end up littered with ifdefs.
 
> @@ -220,6 +235,10 @@ struct ieee80211_bss_conf {
>  	s32 cqm_rssi_thold;
>  	u32 cqm_rssi_hyst;
>  	enum nl80211_channel_type channel_type;
> +#ifdef CONFIG_INET
> +	__be32 arp_addr_list[IEEE80211_BSS_ARP_ADDR_LIST_LEN];
> +	u8 arp_addr_cnt;
> +#endifs

same here.

> @@ -851,6 +851,10 @@ static void ieee80211_set_associated(struct ieee80211_sub_if_data *sdata,
>  	    sdata->vif.bss_conf.cqm_rssi_thold)
>  		bss_info_changed |= BSS_CHANGED_CQM;
>  
> +#ifdef CONFIG_INET
> +	bss_info_changed |= BSS_CHANGED_ARP_ADDR_LIST;
> +#endif
> +

I don't see why you can't set that unconditionally here either, it'll
just be an empty list always.

Otherwise looks pretty good.

johannes


  reply	other threads:[~2010-06-08  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  6:24 [RFC PATCHv2] mac80211: Fix circular locking dependency in ARP filter handling Juuso Oikarinen
2010-06-08  8:03 ` Johannes Berg [this message]
2010-06-08  8:46   ` Juuso Oikarinen

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=1275984236.3706.45.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=juuso.oikarinen@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --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