From: Ben Greear <greearb@candelatech.com>
To: Eliad Peller <eliad@wizery.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] mac80211: fix remain_off_channel regression
Date: Mon, 25 Jul 2011 10:13:31 -0700 [thread overview]
Message-ID: <4E2DA43B.4000206@candelatech.com> (raw)
In-Reply-To: <1311607763-12603-2-git-send-email-eliad@wizery.com>
On 07/25/2011 08:29 AM, Eliad Peller wrote:
> i'm not familiar enough with the off_channel flow,
> but this one looks completely broken - we should
> remain_off_channel if the work was started, and
> the work's channel and channel_type are the same
> as local->tmp_channel and local->tmp_channel_type.
>
> however, if wk->chan_type and local->tmp_channel_type
> coexist (e.g. have the same channel type), we won't
> remain_off_channel.
>
> this behavior was introduced by commit da2fd1f
> ("mac80211: Allow work items to use existing
> channel type.")
This patch looks correct to me.
Thanks,
Ben
>
> Signed-off-by: Eliad Peller<eliad@wizery.com>
> ---
> net/mac80211/work.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/mac80211/work.c b/net/mac80211/work.c
> index a94b312..3291958 100644
> --- a/net/mac80211/work.c
> +++ b/net/mac80211/work.c
> @@ -1068,8 +1068,8 @@ static void ieee80211_work_work(struct work_struct *work)
> continue;
> if (wk->chan != local->tmp_channel)
> continue;
> - if (ieee80211_work_ct_coexists(wk->chan_type,
> - local->tmp_channel_type))
> + if (!ieee80211_work_ct_coexists(wk->chan_type,
> + local->tmp_channel_type))
> continue;
> remain_off_channel = true;
> }
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-07-25 17:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 15:29 [RFC 0/2] mac80211 offchannel fixes Eliad Peller
2011-07-25 15:29 ` [RFC 1/2] mac80211: fix remain_off_channel regression Eliad Peller
2011-07-25 17:13 ` Ben Greear [this message]
2011-08-09 12:13 ` Johannes Berg
2011-08-09 12:48 ` Eliad Peller
2011-08-09 12:55 ` Johannes Berg
2011-10-19 18:03 ` Ben Greear
2011-10-20 16:47 ` Eliad Peller
2011-07-25 15:29 ` [RFC 2/2] mac80211: config hw when going back on-channel Eliad Peller
2011-07-25 17:18 ` Ben Greear
2011-07-25 19:16 ` Eliad Peller
2011-07-25 19:56 ` Ben Greear
2011-07-25 20:07 ` Eliad Peller
2011-07-26 4:39 ` Ben Greear
2011-07-26 5:48 ` Eliad Peller
2011-08-09 12:14 ` Johannes Berg
2011-08-09 13:27 ` Ben Greear
2011-08-09 13:28 ` Johannes Berg
2011-08-09 13:33 ` Ben Greear
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=4E2DA43B.4000206@candelatech.com \
--to=greearb@candelatech.com \
--cc=eliad@wizery.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).