linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: clanctot@codeaurora.org
To: "Arik Nemtsov" <arik@wizery.com>
Cc: "Chet Lanctot" <clanctot@codeaurora.org>,
	"John Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] nl80211/cfg80211: Add support for drivers with AP SME that require PMF SA Query assistance
Date: Tue, 10 Dec 2013 22:07:38 -0000	[thread overview]
Message-ID: <3121017861fe910940c6b44994156635.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CA+XVXfc1ryVcfqsMOc_592iEGYmpP4x3F_w88-10Ky4YG7zZmQ@mail.gmail.com>

Arik,

Thank you for catching this and passing it along.  Yes, it is not non
purpose.  It is due to an error when I entered the changes. 
NL80211_STA_FLAG_NO_SA_QUERY_REQUIRED is the correct name, but it should
have been that name from the beginning.

I also noticed that I did not break the changes up between the two commits
correctly.  I have fixed that.

I will now send out a new set of patch files for review.

-	Chet


> On Tue, Dec 3, 2013 at 6:46 AM, Chet Lanctot <clanctot@codeaurora.org>
> wrote:
>> This adds support for drivers that have AP SME integrated but do
>> not implement the SA Query procedure that is part of Protected
>> Management Frames (PMF, 802.11w).
>>
>> Instead, hostapd can be used to assist drivers that lack SA Query
>> Procedure handling on their own by allowing them to specify this as
>> a device capability flag.
>>
>> Also, a station flag is added to let hostapd indicate to the driver
>> that the SA Query procedure is complete and the driver can process
>> association requests from the station normally.
> [...]
>>   * enum nl80211_feature_flags - device/driver features
>> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
>> index 587ff84..14a14d4 100644
>> --- a/net/wireless/nl80211.c
>> +++ b/net/wireless/nl80211.c
>> @@ -3766,7 +3766,8 @@ int cfg80211_check_station_change(struct wiphy
>> *wiphy,
>>                                   BIT(NL80211_STA_FLAG_ASSOCIATED) |
>>                                   BIT(NL80211_STA_FLAG_SHORT_PREAMBLE) |
>>                                   BIT(NL80211_STA_FLAG_WME) |
>> -                                 BIT(NL80211_STA_FLAG_MFP)))
>> +                                 BIT(NL80211_STA_FLAG_MFP) |
>> +
>> BIT(NL80211_STA_FLAG_SA_QUERY_REQUIRED)))
>
> I didn't really read the patch, but noticed you're adding
> NL80211_STA_FLAG_SA_QUERY_REQUIRED here and changing it to
> NL80211_STA_FLAG_NO_SA_QUERY_REQUIRED in the next one.
> Pretty sure that's not on purpose :)
>
> Arik
>



  reply	other threads:[~2013-12-10 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  4:46 [PATCH 0/2 V2] nl80211/cfg80211: Support PMF on drivers with integrated AP SME Chet Lanctot
2013-12-03  4:46 ` [PATCH 1/2 V2] nl80211/cfg80211: Add support for drivers with AP SME that require PMF SA Query assistance Chet Lanctot
2013-12-03  6:51   ` Arik Nemtsov
2013-12-10 22:07     ` clanctot [this message]
2013-12-03  4:46 ` [PATCH 2/2 V2] nl80211/cfg80211: Enable station PMF requirement to be specified to driver with AP SME Chet Lanctot

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=3121017861fe910940c6b44994156635.squirrel@www.codeaurora.org \
    --to=clanctot@codeaurora.org \
    --cc=arik@wizery.com \
    --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;
as well as URLs for NNTP newsgroup(s).